Adaptive Trust Profile Reference Architecture

ABSTRACT

A system, method, and computer-readable medium are disclosed for monitoring actions of an entity. In various embodiments the monitoring includes: monitoring a plurality of electronically-observable actions of the entity, the plurality of electronically-observable actions of the entity corresponding to a plurality of events enacted by the entity; associating the plurality of events enacted by the entity with a story; and, using the story to derive an inference regarding the entity.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates in general to the field of computers and similar technologies, and in particular to software utilized in this field. Still more particularly, it relates to a method, system and computer-usable medium for using entity profile attributes to adaptively mitigate risk.

Description of the Related Art

Users interact with physical, system, data, and services resources of all kinds, as well as each other, on a daily basis. Each of these interactions, whether accidental or intended, poses some degree of security risk, depending on the behavior of the user. In particular, the actions of a formerly trusted user may become malicious as a result of being subverted, compromised or radicalized due to any number of internal or external factors or stressors. For example, financial pressure, political idealism, irrational thoughts, or other influences may adversely affect a user's intent and/or behavior.

SUMMARY OF THE INVENTION

In one embodiment the invention relates to a method for monitoring actions of an entity, comprising: monitoring a plurality of electronically-observable actions of the entity, the plurality of electronically-observable actions of the entity corresponding to a plurality of events enacted by the entity; associating the plurality of events enacted by the entity with a story; and, using the story to derive an inference regarding the entity.

In another embodiment the invention relates to a system comprising: a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: monitoring a plurality of electronically-observable actions of the entity, the plurality of electronically-observable actions of the entity corresponding to a plurality of events enacted by the entity; associating the plurality of events enacted by the entity with a story; and, using the story to derive an inference regarding the entity.

In another embodiment the invention relates to a computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: monitoring a plurality of electronically-observable actions of the entity, the plurality of electronically-observable actions of the entity corresponding to a plurality of events enacted by the entity; associating the plurality of events enacted by the entity with a story; and, using the story to derive an inference regarding the entity.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.

FIG. 1 depicts an exemplary client computer in which the present invention may be implemented;

FIG. 2 is a simplified block diagram of an edge device;

FIG. 3 is a simplified block diagram of an endpoint agent;

FIG. 4 is a simplified block diagram of a security analytics system;

FIG. 5 is a simplified block diagram of a security analytics system;

FIG. 6 is a simplified block diagram of an adaptive trust profile (ATP);

FIG. 7 is simplified block diagram of process flows associated with the operation of an ATP system;

FIGS. 8 a and 8 b shows a block diagram of a security analytics system environment;

FIG. 9 shows a functional block diagram of the operation of an ATP system;

FIG. 10 is a table showing components of an ATP;

FIG. 11 is a table showing analytic utility actions occurring during a session;

FIG. 12 is a simplified block diagram of an ATP system environment;

FIG. 13 is a generalized flowchart of the performance of session-based fingerprint generation operations;

FIGS. 14 a and 14 b are a generalized flowchart of the performance of ATP definition and management operations;

FIG. 15 is a simplified block diagram of a security analytics system implemented to adaptively assess risk associated with an entity behavior;

FIG. 16 is a simplified block diagram of the operation of a security analytics system to adaptively respond to an entity request;

FIG. 17 is a generalized flowchart of the performance of security analytics system operations for adaptively managing entity behavior risk; and

FIG. 18 is a generalized flowchart of the performance of story association operations.

DETAILED DESCRIPTION

A method, system and computer-usable medium are disclosed for using entity profile attributes to adaptively mitigate risk. Certain aspects of the invention include an appreciation that the existence of any entity, whether it is an individual user, a group of users, an organization, a device, a system, a network, an account, a domain, an operation, a process, a software application, or a service, represents some degree of security risk. Various aspects of the invention likewise include an appreciation that certain non-user entities, such as computing, communication, and surveillance devices can be a source for telemetry associated with certain events and entity behaviors. Likewise, various aspects of the invention include an appreciation that certain accounts may be global, spanning multiple devices, such as a domain-level account allowing an entity access to multiple systems. Certain aspects of the invention likewise include an appreciation that a particular account may be shared by multiple entities.

Accordingly, certain aspects of the invention include an appreciation that a particular entity can be assigned a measure of risk according to its respective attributes, associated behavioral models, and resultant inferences contained in an associated profile. As an example, a first profile may have an attribute that its corresponding entity works in the human resource department, while a second profile may have an attribute that its corresponding entity is an email server. To continue the example, the first profile may have an associated behavioral model that indicates its corresponding entity is not acting as they did the day before, while the second profile may have an associated behavioral model that indicates its corresponding entity is connecting to a suspicious IP address. To further continue the example, the first profile may have a resultant inference that its corresponding entity is likely to be leaving the company, while the second profile may have a resultant inference that there is a high probability its corresponding entity is compromised. Certain embodiments of the invention likewise include an appreciation that the measure of risk assigned to a particular entity can be adaptively revised according to corresponding changes in its respective attributes, associated behavioral models, and resultant inferences contained in an associated profile.

For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a mobile device such as a tablet or smartphone, a consumer electronic device, a connected “smart device,” a network appliance, a network storage device, a network gateway device, a server or collection of servers or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include volatile and/or non-volatile memory, and one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage systems, one or more wired or wireless interfaces for communicating with other networked devices, external devices, and various input and output (I/O) devices, such as a keyboard, a mouse, a microphone, speakers, a track pad, a touchscreen and a display device (including a touch sensitive display device). The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or solid state drive), a sequential access storage device (e.g., a tape disk drive), optical storage device, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

FIG. 1 is a generalized illustration of an information handling system 100 that can be used to implement the system and method of the present invention. The information handling system 100 includes a processor (e.g., central processor unit or “CPU”) 102, input/output (I/O) devices 104, such as a display, a keyboard, a mouse, and associated controllers, a storage system 106, and various other subsystems 108. In various embodiments, the information handling system 100 also includes network port 110 operable to connect to a network 140, which is likewise accessible by a service provider server 142. The information handling system 100 likewise includes system memory 112, which is interconnected to the foregoing via one or more buses 114. System memory 112 further includes operating system (OS) 116 and in various embodiments may also include a security analytics system 118. In one embodiment, the information handling system 100 is able to download the security analytics system 118 from the service provider server 142. In another embodiment, the security analytics system 118 is provided as a service from the service provider server 142.

In various embodiments, the security analytics system 118 performs a security analytics operation. In certain embodiments, the security analytics operation improves processor efficiency, and thus the efficiency of the information handling system 100, by facilitating security analytics functions. As will be appreciated, once the information handling system 100 is configured to perform the security analytics operation, the information handling system 100 becomes a specialized computing device specifically configured to perform the security analytics operation and is not a general purpose computing device. Moreover, the implementation of the security analytics system 118 on the information handling system 100 improves the functionality of the information handling system 100 and provides a useful and concrete result of performing security analytics functions to mitigate security risk. In certain embodiments, the security analytics system 118 may be implemented to include an adaptive trust profile (ATP) system 120. In certain embodiments, the ATP system 120 may be implemented to perform various ATP operations, described in greater detail herein.

FIG. 2 is a simplified block diagram of an edge device implemented in accordance with an embodiment of the invention. As used herein, an edge device, such as the edge device 202 shown in FIG. 2 , broadly refers to a device providing an entry point into a network 140. Examples of such edge devices 202 may include routers, routing switches, integrated access devices (IADs), multiplexers, wide-area network (WAN) access devices, and network security appliances. In certain embodiments, the network 140 may be a private network (e.g., an enterprise network), a semi-public network (e.g., a service provider core network), or a public network (e.g., the Internet).

Skilled practitioners of the art will be aware that edge devices 202 are often implemented as routers that provide authenticated access to faster, more efficient backbone and core networks. Furthermore, current industry trends include making edge devices 202 more intelligent, which allows core devices to operate at higher speed as they are not burdened with additional administrative overhead. Accordingly, such edge devices 202 often include Quality of Service (QoS) and multi-service functions to manage different types of traffic. Consequently, it is common to design core networks with switches that use routing protocols such as Open Shortest Path First (OSPF) or Multiprotocol Label Switching (MPLS) for reliability and scalability. Such approaches allow edge devices 202 to have redundant links to the core network, which not only provides improved reliability, but enables enhanced, flexible, and scalable security capabilities as well.

In certain embodiments, the edge device 202 may be implemented to include a communications/services architecture 204, various pluggable capabilities 212, a traffic router 210, and a pluggable hosting framework 208. In certain embodiments, the communications/services architecture 202 may be implemented to provide access to and from various networks 140, cloud services 206, or a combination thereof. In certain embodiments, the cloud services 206 may be provided by a cloud infrastructure familiar to those of skill in the art. In certain embodiments, the edge device 202 may be implemented to provide support for a variety of generic services, such as directory integration, logging interfaces, update services, and bidirectional risk/context flows associated with various analytics. In certain embodiments, the edge device 202 may be implemented to provide temporal information, described in greater detail herein, associated with the provision of such services.

In certain embodiments, the edge device 202 may be implemented as a generic device configured to host various network communications, data processing, and security management capabilities. In certain embodiments, the pluggable hosting framework 208 may be implemented to host such capabilities in the form of pluggable capabilities 212. In certain embodiments, the pluggable capabilities 212 may include capability ‘1’ 214 (e.g., basic firewall), capability ‘2’ 216 (e.g., general web protection), capability ‘3’ 218 (e.g., data sanitization), and so forth through capability ‘n’ 220, which may include capabilities needed for a particular operation, process, or requirement on an as-needed basis. In certain embodiments, such capabilities may include the performance of operations associated with managing an adaptive trust Profile (ATP), described in greater detail herein. In certain embodiments, such operations may include the provision of associated temporal information (e.g., time stamps).

In certain embodiments, the pluggable capabilities 212 may be sourced from various cloud services 206. In certain embodiments, the pluggable hosting framework 208 may be implemented to provide certain computing and communication infrastructure components, and foundation capabilities, required by one or more of the pluggable capabilities 212. In certain embodiments, the pluggable hosting framework 208 may be implemented to allow the pluggable capabilities 212 to be dynamically invoked. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 3 is a simplified block diagram of an endpoint agent implemented in accordance with an embodiment of the invention. As used herein, an endpoint agent 306 broadly refers to a software agent used in combination with an endpoint device 304 to establish a protected endpoint 302. Skilled practitioners of the art will be familiar with software agents, which are computer programs that perform actions on behalf of a user or another program. In various approaches, a software agent may be autonomous or work together with another agent or a user. In certain of these approaches the software agent is implemented to autonomously decide if a particular action is appropriate for a given event, such as an observed entity behavior.

An endpoint device 304, as likewise used herein, refers to an information processing system such as a personal computer, a laptop computer, a tablet computer, a personal digital assistant (PDA), a smart phone, a mobile telephone, a digital camera, a video camera, or other device capable of storing, processing and communicating data. In certain embodiments, the communication of the data may take place in real-time or near-real-time. As used herein, real-time broadly refers to processing and providing information within a time interval brief enough to not be discernable by a user. As an example, a cellular phone conversation may be used to communicate information in real-time, while an instant message (IM) exchange may be used to communicate information in near real-time. In certain embodiments, the communication of the information may take place asynchronously. For example, an email message may be stored on an endpoint device 304 when it is offline. In this example, the information may be communicated to its intended recipient once the endpoint device 304 gains access to a network 140.

A protected endpoint 302, as likewise used herein, broadly refers to a policy-based approach to network security that typically requires endpoint devices 304 to comply with certain criteria before they are granted access to network resources. As an example, a given endpoint device 304 may be required to have a particular operating system (OS), or version thereof, a Virtual Private Network (VPN) client, anti-virus software with current updates, and so forth. In certain embodiments, the protected endpoint 302 may be implemented to perform operations associated with providing real-time resolution of the identity of an entity at a particular point in time, as described in greater detail herein. In certain embodiments, the protected endpoint 302 may be implemented to provide temporal information, such as timestamp information, associated with such operations.

In certain embodiments, the real-time resolution of the identity of an entity at a particular point in time may be based upon contextual information associated with a given entity behavior. As used herein, contextual information broadly refers to any information, directly or indirectly, individually or in combination, related to a particular entity behavior. In certain embodiments, entity behavior may include an entity's physical behavior, cyber behavior, or a combination thereof. As likewise used herein, physical behavior broadly refers to any entity behavior occurring within a physical realm. More particularly, physical behavior may include any action enacted by an entity that can be objectively observed, or indirectly inferred, within a physical realm.

As an example, a user may attempt to use an electronic access card to enter a secured building at a certain time. In this example, the use of the access card to enter the building is the action and the reading of the access card makes the user's physical behavior electronically-observable. As another example, a first user may physically transfer a document to a second user, which is captured by a video surveillance system. In this example, the physical transferal of the document from the first user to the second user is the action. Likewise, the video record of the transferal makes the first and second user's physical behavior electronically-observable. As used herein, entity behavior broadly refers to one or more actions, enacted individually or in combination, by an entity. As likewise used herein, electronically-observable entity behavior broadly refers to any behavior exhibited or enacted by an entity that can be observed, directly or indirectly, by electronic means.

Cyber behavior, as used herein, broadly refers to any behavior occurring in cyberspace, whether enacted by an individual user, a group of users, or a system acting at the behest of an individual user, a group of users, or other entity. More particularly, cyber behavior may include physical, social, or mental actions that can be objectively observed, or indirectly inferred, within cyberspace. As an example, a user may use an endpoint device 304 to access and browse a particular website on the Internet. In this example, the individual actions performed by the user to access and browse the website constitute a cyber behavior. As another example, a user may use an endpoint device 304 to download a data file from a particular system at a particular point in time. In this example, the individual actions performed by the user to download the data file, and associated temporal information, such as a time-stamp associated with the download, constitute a cyber behavior. In these examples, the actions are enacted within cyberspace, which makes them electronically-observable.

As likewise used herein, cyberspace broadly refers to a network 140 environment capable of supporting communication between two or more entities. In certain embodiments, the entity may be a user, an endpoint device 304, or various resources, described in greater detail herein. In certain embodiments, the entities may include various endpoint devices 304 or resources operating at the behest of an entity, such as a user. In certain embodiments, the communication between the entities may include audio, image, video, text, or binary data.

As described in greater detail herein, the contextual information may include a user's authentication factors. Contextual information may likewise include various temporal identity resolution factors, such as identification factors associated with the entity, the date/time/frequency of various entity behaviors, the entity's location, the entity's role or position in an organization, their associated access rights, and certain user gestures employed by a user in the enactment of a user behavior. Other contextual information may likewise include various user interactions, whether the interactions are with an endpoint device 304, a network 140, a resource, or another user. In certain embodiments, entity behaviors, and their related contextual information, may be collected at particular points of observation, and at particular points in time, described in greater detail herein. In certain embodiments, a protected endpoint 302 may be implemented as a point of observation for the collection of entity behavior and contextual information.

In certain embodiments, the endpoint agent 306 may be implemented to universally support a variety of operating systems, such as Apple Macintosh®, Microsoft Windows®, Linux®, Android® and so forth. In certain embodiments, the endpoint agent 306 may be implemented to interact with the endpoint device 304 through the use of low-level hooks 312 at the operating system level. It will be appreciated that the use of low-level hooks 312 allows the endpoint agent 306 to subscribe to multiple events through a single hook. Consequently, multiple functionalities provided by the endpoint agent 306 can share a single data stream, using only those portions of the data stream they may individually need. Accordingly, system efficiency can be improved and operational overhead reduced.

In certain embodiments, the endpoint agent 306 may be implemented to provide a common infrastructure for pluggable feature packs 308. In various embodiments, the pluggable feature packs 308 may provide certain security management functionalities. Examples of such functionalities may include various anti-virus and malware detection, data loss protection (DLP), insider threat detection, and so forth. In certain embodiments, the security management functionalities may include one or more functionalities associated with providing real-time resolution of the identity of an entity at a particular point in time, as described in greater detail herein.

In certain embodiments, a particular pluggable feature pack 308 is invoked as needed by the endpoint agent 306 to provide a given functionality. In certain embodiments, individual features of a particular pluggable feature pack 308 are invoked as needed. It will be appreciated that the ability to invoke individual features of a pluggable feature pack 308, without necessarily invoking all such features, will likely improve the operational efficiency of the endpoint agent 306 while simultaneously reducing operational overhead. Accordingly, the endpoint agent 306 can self-optimize in certain embodiments by using the common infrastructure and invoking only those pluggable components that are applicable or needed for a given user behavior.

In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 according to the occurrence of a particular user behavior. In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 according to the occurrence of a particular temporal event, described in greater detail herein. In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 at a particular point in time. In these embodiments, the method by which a given user behavior, temporal event, or point in time is selected is a matter of design choice.

In certain embodiments, the individual features of a pluggable feature pack 308 may be invoked by the endpoint agent 306 according to the context of a particular user behavior. As an example, the context may be the user enacting the user behavior, their associated risk classification, which resource they may be requesting, the point in time the user behavior is enacted, and so forth. In certain embodiments, the pluggable feature packs 308 may be sourced from various cloud services 206. In certain embodiments, the pluggable feature packs 308 may be dynamically sourced from various cloud services 206 by the endpoint agent 306 on an as-need basis.

In certain embodiments, the endpoint agent 306 may be implemented with additional functionalities, such as event analytics 310. In certain embodiments, the event analytics 310 functionality may include analysis of various user behaviors, described in greater detail herein. In certain embodiments, the endpoint agent 306 may be implemented with a thin hypervisor 314, which can be run at Ring-1, thereby providing protection for the endpoint agent 306 in the event of a breach. As used herein, a thin hypervisor broadly refers to a simplified, OS-dependent hypervisor implemented to increase security. As likewise used herein, Ring-1 broadly refers to approaches allowing guest operating systems to run Ring 0 (i.e., kernel) operations without affecting other guests or the host OS. Those of skill in the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 4 is a simplified block diagram of a security analytics system implemented in accordance with an embodiment of the invention. In certain embodiments, the security analytics system 118 shown in FIG. 4 may include an event queue analytics 404 module, described in greater detail herein. In certain embodiments, the event queue analytics 404 sub-system may be implemented to include an enrichment 406 module and a streaming analytics 408 module. In certain embodiments, the security analytics system 118 may be implemented to provide log storage, reporting, and analytics capable of performing streaming 408 and on-demand 410 analytics operations. In certain embodiments, such operations may be associated with defining and managing an adaptive trust profile (ATP), detecting entity behavior that may be of analytic utility, adaptively responding to mitigate risk, or a combination thereof, as described in greater detail herein.

As used herein, analytic utility broadly refers to anything that may be analyzed to produce a useful result. In certain embodiments, such analysis may involve approaches known to those of skill in the art for using mathematics, statistics, predictive modeling, and various machine learning techniques to find meaningful patterns and knowledge in a particular set of data. In various embodiments, such analysis may likewise involve analyzing historical data to research potential trends, the effects of certain entity behavior, interactions, decisions or associated events, evaluation of a particular scenario, described in greater detail herein, or a combination thereof. In certain embodiments, entity behavior of analytic utility may be determined to be anomalous, abnormal, unexpected, malicious, or some combination thereof, as likewise described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented to provide a uniform platform for storing events and contextual information associated with various entity behaviors and performing longitudinal analytics. As used herein, longitudinal analytics broadly refers to performing analytics of entity behaviors occurring over a particular period of time. As an example, an entity may iteratively attempt to access certain proprietary information stored in various locations. In addition, the attempts may occur over a brief period of time. To continue the example, the fact that the information the entity is attempting to access is proprietary, that it is stored in various locations, and the attempts are occurring in a brief period of time, in combination, may indicate the entity behavior enacted by the entity is suspicious. As another example, certain entity identifier information (e.g., a user name) associated with an entity may change over time. In this example, a change in the entity's user name, during a particular period of time or at a particular point in time, may represent suspicious entity behavior.

In certain embodiments, the security analytics system 118 may be implemented to be scalable. In certain embodiments, the security analytics system 118 may be implemented in a centralized location, such as a corporate data center. In these embodiments, additional resources may be added to the security analytics system 118 as needs grow. In certain embodiments, the security analytics system 118 may be implemented as a distributed system. In these embodiments, the security analytics system 118 may span multiple information handling systems. In certain embodiments, the security analytics system 118 may be implemented in a cloud environment. In certain embodiments, the security analytics system 118 may be implemented in a virtual machine (VM) environment. In such embodiments, the VM environment may be configured to dynamically and seamlessly scale the security analytics system 118 as needed. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In certain embodiments, an event stream collector 402 may be implemented to collect event and related contextual information, described in greater detail herein, associated with various entity behaviors. In these embodiments, the method by which the event and contextual information is selected to be collected by the event stream collector 402 is a matter of design choice. In certain embodiments, the event and contextual information collected by the event stream collector 402 may be processed by an enrichment module 406 to generate enriched entity behavior information. In certain embodiments, the enrichment may include certain contextual information related to a particular entity behavior or event. In certain embodiments, the enrichment may include certain temporal information, such as timestamp information, related to a particular entity behavior or event.

In certain embodiments, enriched entity behavior information may be provided by the enrichment module 406 to a streaming 408 analytics module. In turn, the streaming 408 analytics module may provide some or all of the enriched entity behavior information to an on-demand 410 analytics module. As used herein, streaming 408 analytics broadly refers to analytics performed in near real-time on enriched entity behavior information as it is received. Likewise, on-demand 410 analytics broadly refers herein to analytics performed, as they are requested, on enriched entity behavior information after it has been received. In certain embodiments, the enriched entity behavior information may be associated with a particular event. In certain embodiments, the enrichment 406 and streaming analytics 408 modules may be implemented to perform event queue analytics 404 operations, as described in greater detail herein.

In certain embodiments, the on-demand 410 analytics may be performed on enriched entity behavior associated with a particular interval of, or point in, time. In certain embodiments, the streaming 408 or on-demand 410 analytics may be performed on enriched entity behavior associated with a particular user, group of users, one or more non-user entities, or a combination thereof. In certain embodiments, the streaming 408 or on-demand 410 analytics may be performed on enriched entity behavior associated with a particular resource, such as a facility, system, datastore, or service. Those of skill in the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In certain embodiments, the results of various analytics operations performed by the streaming 408 or on-demand 410 analytics modules may be provided to a storage Application Program Interface (API) 414. In turn, the storage API 414 may be implemented to provide access to various datastores ‘1’ 416 through ‘n’ 418, which in turn are used to store the results of the analytics operations. In certain embodiments, the security analytics system 118 may be implemented with a logging and reporting front-end 412, which is used to receive the results of analytics operations performed by the streaming 408 analytics module. In certain embodiments, the datastores ‘1’ 416 through ‘n’ 418 may variously include a datastore of entity identifiers, temporal events, or a combination thereof.

In certain embodiments, the security analytics system 118 may include a risk scoring 420 module implemented to perform risk scoring operations, described in greater detail herein. In certain embodiments, functionalities of the risk scoring 420 module may be provided in the form of a risk management service 422. In certain embodiments, the risk management service 422 may be implemented to perform operations associated with defining and managing an adaptive trust profile (ATP), as described in greater detail herein. In certain embodiments, the risk management service 422 may be implemented to perform operations associated with detecting entity behavior that may be of analytic utility and adaptively responding to mitigate risk, as likewise described in greater detail herein. In certain embodiments, the risk management service 422 may be implemented to provide the results of various analytics operations performed by the streaming 406 or on-demand 408 analytics modules. In certain embodiments, the risk management service 422 may be implemented to use the storage API 412 to access various enhanced entity behavior and analytics information stored on the datastores ‘1’ 414 through ‘n’ 416. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 5 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention. In certain embodiments, the security analytics system 118 may be implemented to perform operations associated with detecting entity behavior that may be of analytic utility, as described in greater detail herein. In certain embodiments, the security analytics system 118 may be implemented in combination with one or more endpoint agents 306, one or more edge devices 202, various cloud services 206, and a network 140 to perform such operations.

In certain embodiments, the network edge device 202 may be implemented in a bridge, a firewall, or a passive monitoring configuration. In certain embodiments, the edge device 202 may be implemented as software running on an information handling system. In certain embodiments, the network edge device 202 may be implemented to provide integrated logging, updating and control. In certain embodiments, the edge device 202 may be implemented to receive network requests and context-sensitive user behavior information in the form of enriched user behavior information 510, described in greater detail herein, from an endpoint agent 306, likewise described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented as both a source and a sink of user behavior information. In certain embodiments, the security analytics system 118 may be implemented to serve requests for user/resource risk data. In certain embodiments, the edge device 202 and the endpoint agent 306, individually or in combination, may provide certain entity behavior information to the security analytics system 118 using either push or pull approaches familiar to skilled practitioners of the art.

As described in greater detail herein, the edge device 202 may be implemented in certain embodiments to receive enriched user behavior information 510 from the endpoint agent 306. It will be appreciated that such enriched user behavior information 510 will likely not be available for provision to the edge device 202 when an endpoint agent 306 is not implemented for a corresponding endpoint device 304. However, the lack of such enriched user behavior information 510 may be accommodated in various embodiments, albeit with reduced functionality related to operations associated with defining and managing an entity profile, detecting entity behavior that may be normal or of analytic utility, mitigating associated risk, or a combination thereof.

In certain embodiments, a given user behavior may be enriched by an associated endpoint agent 306 attaching contextual information to a request. In certain embodiments, the context is embedded within a network request, which is then provided as enriched user behavior information 510. In certain embodiments, the contextual information may be concatenated, or appended, to a request, which in turn may be provided as enriched user behavior information 510. In these embodiments, the enriched user behavior information 510 may be unpacked upon receipt and parsed to separate the request and its associated contextual information. Certain embodiments of the invention reflect an appreciation that one possible disadvantage of such an approach is that it may perturb certain Intrusion Detection System and/or Intrusion Detection Prevention (IDS/IDP) systems implemented on a network 140.

In certain embodiments, new flow requests may be accompanied by a contextual information packet sent to the edge device 202. In these embodiments, the new flow requests may be provided as enriched user behavior information 510. In certain embodiments, the endpoint agent 306 may also send updated contextual information to the edge device 202 once it becomes available. As an example, an endpoint agent 306 may share a list of files that have been read by a current process at any point in time once the information has been collected. To continue the example, such a list of files may be used to determine which data the endpoint agent 306 may be attempting to exfiltrate.

In certain embodiments, point analytics processes executing on the edge device 202 may request a particular service. As an example, risk scores associated with a particular event on a per-user basis may be requested. In certain embodiments, the service may be requested from the security analytics system 118. In certain embodiments, the service may be requested from various cloud services 206.

In certain embodiments, contextual information associated with a particular entity behavior may be attached to various network service requests. In certain embodiments, the request may be wrapped and then handled by proxy. In certain embodiments, a small packet of contextual information associated with an entity behavior may be sent with a service request. In certain embodiments, service requests may be related to Domain Name Service (DNS), web browsing activity, email, and so forth, all of which are essentially requests for service by an endpoint device 304. In certain embodiments, such service requests may be associated with temporal event information, described in greater detail herein. Consequently, such requests can be enriched by the addition of entity behavior contextual information (e.g., UserAccount, interactive/automated, data-touched, temporal event information, etc.). Accordingly, the edge device 202 can then use this information to manage the appropriate response to submitted requests.

In certain embodiments, the security analytics system 118 may be implemented in different operational configurations. In certain embodiments, the security analytics system 118 may be implemented by using the endpoint agent 306. In certain embodiments, the security analytics system 118 may be implemented by using endpoint agent 306 in combination with the edge device 202. In certain embodiments, the cloud services 206 may likewise be implemented for use by the endpoint agent 306, the edge device 202, and the security analytics system 118, individually or in combination. In these embodiments, the security analytics system 118 may be primarily oriented to performing risk assessment operations related to entity actions, software program actions, data accesses, or a combination thereof. In certain embodiments, software program actions may be treated as a proxy for the entity.

In certain embodiments, the endpoint agent 306 may be implemented to update the security analytics system 118 with user behavior and associated contextual information, thereby allowing an offload of certain analytics processing overhead. In certain embodiments, this approach allows for longitudinal risk scoring, which assesses risk associated with certain user behavior during a particular interval of time. In certain embodiments, the security analytics system 118 may be implemented to access risk scores associated with the same user account, but accrued on different endpoint devices 304. It will be appreciated that such an approach may prove advantageous when an adversary is “moving sideways” through a network environment, using different endpoint devices 304 to collect information.

In certain embodiments, the security analytics system 118 may be primarily oriented to applying risk mitigations in a way that maximizes security effort return-on-investment (ROI). In certain embodiments, this approach may be accomplished by providing additional contextual and entity behavior information associated with entity requests. As an example, a web gateway may not concern itself with why a particular file is being requested by a certain entity at a particular point in time. Accordingly, if the file cannot be identified as malicious or harmless, there is no context available to determine how, or if, to proceed. To extend the example, the edge device 202 and security analytics system 118 may be coupled such that requests can be contextualized and fitted into a framework that evaluates their associated risk. Certain embodiments of the invention reflect an appreciation that such an approach works well with web-based data loss protection (DLP) approaches, as each transfer is no longer examined in isolation, but in the broader context of an identified entity's actions, at a particular time, on the network 140.

As another example, the security analytics system 118 may be implemented to perform risk scoring processes to decide whether to block or allow unusual flows. In various embodiments, the risk scoring processes may be implemented to include certain aspects of eXtensible Access Control Markup Language (XACML) approaches known to skilled practitioners of the art. In certain embodiments, XACML obligations may be implemented to block or allow unusual flows. In certain embodiments, an XACML obligation may be implemented as a directive from a policy decision point (PDP) to a policy enforcement point (PEP) regarding what must be performed before or after a flow is approved. Certain embodiments of the invention reflect an appreciation that such an approach is highly applicable to defending against point-of-sale (POS) malware, a breach technique that has become increasingly more common in recent years. Certain embodiments of the invention likewise reflect an appreciation that while various edge device 202 implementations may not stop all such exfiltrations, they may be able to complicate the task for the attacker.

In certain embodiments, the security analytics system 118 may be primarily oriented to maximally leverage contextual information associated with various entity behaviors within the system. In certain embodiments, data flow tracking is performed by one or more endpoint agents 306, which allows the quantity and type of information associated with particular hosts to be measured. In turn, this information may be used to determine how the edge device 202 handles requests. By contextualizing such entity behavior on the network 140, the security analytics system 118 can provide intelligent protection, making decisions that make sense in the broader context of an organization's activities. Certain embodiments of the invention reflect an appreciation that one advantage to such an approach is that information flowing through an organization, and the networks they employ, should be trackable, and substantial data breaches preventable. Skilled practitioners of the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 6 is a simplified block diagram of an adaptive trust profile implemented in accordance with an embodiment of the invention. As used herein, an adaptive trust profile (ATP) 640 broadly refers to a collection of information that uniquely describes an entity's identity and their associated behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, an ATP 640 may be used to adaptively draw inferences regarding the trustworthiness of an entity. In certain embodiments, as described in greater detail herein, the drawing of the inferences may involve comparing a new entity behavior to known past behaviors enacted by the entity. In certain embodiments, new entity behavior of analytic utility may represent entity behavior that represents a security risk. As likewise used herein, an entity broadly refers to something that exists as itself, whether physically or abstractly. In certain embodiments, an entity may be a user entity, a non-user entity, or a combination thereof. In certain embodiments, the identity of an entity may be known or unknown.

As used herein, a user entity broadly refers to an entity capable of enacting a user behavior, as described in greater detail herein. Examples of a user entity include an individual person, a group of people, an organization, or a government. As likewise used herein, a non-user entity broadly refers to an entity whose identity can be described and may exhibit certain behavior, but is incapable of enacting a user behavior. Examples of a non-user entity include an item, a device, such as endpoint and edge devices, a network, an account, a domain, an operation, and a process. Other examples of a non-user entity include a resource, such as a geographical location or formation, a physical facility, a venue, a system, a software application, a data store, and a service, such as a service operating in a cloud environment.

In certain embodiments, an electronically-observable action of an entity corresponding to an event enacted by the entity may be monitored. In certain embodiments, a security analytics system 118, described in greater detail herein, may be implemented to perform the monitoring of such an electronically-observable action. In certain embodiments, the electronically observed actions may be combined with temporal information, likewise described in greater detail herein, to generate time-stamped electronically-observed actions. In certain embodiments, the electronically-observable action of an entity may be converted into electronic information representing the action of the entity. In certain embodiments, the resulting electronic information may be used to generate an associated ATP 640.

Certain embodiments of the invention reflect an appreciation that being able to uniquely identity a device may assist in establishing whether or not a particular login is legitimate. As an example, user impersonations may not occur at the user's endpoint, but rather, from another device or system. Certain embodiments of the invention likewise reflect an appreciation that profiling the behavior of a particular device or system may assist in determining whether or not it is acting suspiciously.

In certain embodiments, an account may be local account, which runs on a single machine. In certain embodiments, an account may be a global account, providing access to multiple resources. In certain embodiments, a process may be implemented to run in an unattended mode, such as when backing up files or checking for software updates. Certain embodiments of the invention reflect an appreciation that it is often advantageous to track events at the process level as a method of determining which events are associated with background processes and which are initiated by a user entity.

In certain embodiments, an ATP 640 may be implemented to include a user entity profile 602, an associated user entity mindset profile 632, a non-user entity profile 634, and an entity state 638, or a combination thereof. As used herein, a user entity profile 602 broadly refers to a collection of information that uniquely describes a user entity's identity and their associated behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, as described in greater detail herein, the user entity profile 602 may include user profile attributes 612, user behavior factors 614, and user mindset factors 626, or a combination thereof. In certain embodiments, the user profile attributes 612 may include certain user authentication factors 604, described in greater detail herein, and personal information 608.

As used herein, a user profile attribute 612 broadly refers to data or metadata that can be used, individually or in combination with other user profile attributes 612, user behavior factors 614, or user mindset factors 626, to ascertain the identity of a user entity. In various embodiments, certain user profile attributes 612 may be uniquely associated with a particular user entity. In certain embodiments, the personal information 608 may include non-sensitive personal information associated with a user entity, such as their name, title, position, role, and responsibilities. In certain embodiments, the personal information 608 may likewise include technical skill level information, peer information, expense account information, paid time off (PTO) information, data analysis information, insider information, misconfiguration information, third party information, or a combination thereof. In certain embodiments, the personal information 608 may contain sensitive personal information associated with a user entity. As used herein, sensitive personal information (SPI), also commonly referred to as personally identifiable information (PII), broadly refers to any information usable to ascertain the identity of a user entity, either by itself, or in combination with other information, such as contextual information described in greater detail herein.

Examples of SPI may include the full or legal name of a user entity, initials or nicknames, place and date of birth, home and business addresses, personal and business telephone numbers, their gender, and other genetic information. Additional examples of SPI may include government-issued identifiers, such as a Social Security Number (SSN) or a passport number, vehicle registration plate and serial numbers, and driver's license numbers. Other examples of SPI may include certain email addresses and social media identifiers, credit and debit card numbers, and other digital identity information. Yet other examples of SPI may include employer-issued identifiers, financial transaction information, credit scores, electronic medical records (EMRs), insurance claim information, personal correspondence, and so forth. Further examples of SPI may include user authentication factors 604, such as biometrics, user identifiers and passwords, and personal identification numbers (PINs).

In certain embodiments, the SPI may include information considered by an individual user, a group of users, or an organization (e.g., a company, a government or non-government organization, etc.), to be confidential or proprietary. One example of such confidential information is protected health information (PHI). As used herein, PHI broadly refers to any information associated with the health status, provision of health care, or payment for health care that is created or collected by a “covered entity,” or an associate thereof, that can be linked to a particular individual. As likewise used herein, a “covered entity” broadly refers to health plans, healthcare clearinghouses, healthcare providers, and others, who may electronically communicate any health-related information associated with a particular individual. Examples of such PHI may include any part of a patient's medical record, healthcare record, or payment history for medical or healthcare services.

As used herein, a user behavior factor 614 broadly refers to information associated with a user entity's behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, user behavior factors 614 may include the user entity's access rights 616, the user entity's interactions 618, and the date/time/frequency 620 of when the interactions 618 are enacted. In certain embodiments, the user behavior factors 614 may likewise include the user entity's location 622, and the gestures 624 used by the user entity to enact the interactions 618.

In certain embodiments, the user entity gestures 624 may include key strokes on a keypad, a cursor movement, a mouse movement or click, a finger swipe, tap, or other hand gesture, an eye movement, or some combination thereof. In certain embodiments, the user entity gestures 624 may likewise include the cadence of the user's keystrokes, the motion, force and duration of a hand or finger gesture, the rapidity and direction of various eye movements, or some combination thereof. In certain embodiments, the user entity gestures 624 may include various audio or verbal commands performed by the user.

As used herein, user mindset factors 626 broadly refer to information used to make inferences regarding the mental state of a user entity at a particular point in time, during the occurrence of an event or an enactment of a user behavior, or a combination thereof. As likewise used herein, mental state broadly refers to a hypothetical state corresponding to the way a user entity may be thinking or feeling. Likewise, as used herein, an event broadly refers to the occurrence of action performed by an entity. In certain embodiments, the user entity mindset factors 626 may include a personality type 628. Examples of known approaches for determining a personality type 628 include Jungian types, Myers-Briggs type indicators, Keirsy Temperament Sorter, Socionics, Enneagram of Personality, and Eyseneck's three-factor model.

In certain embodiments, the user mindset factors 626 may include various behavioral biometrics 630. As used herein, a behavioral biometric 626 broadly refers to a physiological indication of a user entity's mental state. Examples of behavioral biometrics 630 may include a user entity's blood pressure, heart rate, respiratory rate, eye movements and iris dilation, facial expressions, body language, tone and pitch of voice, speech patterns, and so forth.

Certain embodiments of the invention reflect an appreciation that certain user behavior factors 614, such as user entity gestures 624, may provide additional information related to inferring a user entity's mental state. As an example, a user entering text at a quick pace with a rhythmic cadence may indicate intense focus. Likewise, an individual user intermittently entering text with forceful keystrokes may indicate the user is in an agitated state. As another example, the user may intermittently enter text somewhat languorously, which may indicate being in a thoughtful or reflective state of mind. As yet another example, the user may enter text with a light touch with an uneven cadence, which may indicate the user is hesitant or unsure of what is being entered.

Certain embodiments of the invention likewise reflect an appreciation that while the user entity gestures 624 may provide certain indications of the mental state of a particular user entity, they may not provide the reason for the user entity to be in a particular mental state. Likewise, certain embodiments of the invention include an appreciation that certain user entity gestures 624 and behavioral biometrics 630 are reflective of an individual user's personality type 628. As an example, aggressive, forceful keystrokes combined with an increased heart rate may indicate normal behavior for a particular user when composing end-of-month performance reviews. In various embodiments, certain user entity behavior factors 614, such as user gestures 624, may be correlated with certain contextual information, as described in greater detail herein.

In certain embodiments, a security analytics system 118, described in greater detail herein, may be implemented to include an adaptive trust profile (ATP) system 120. In certain embodiments, the ATP system 120 may be implemented to use a user entity profile 602 in combination with an entity state 638 to generate a user entity mindset profile 632. As used herein, entity state 638 broadly refers to the context of a particular event or entity behavior. In certain embodiments, the entity state 638 may be a long-term entity state or a short-term entity state. As used herein, a long-term entity state 638 broadly relates to an entity state 638 that persists for an extended interval of time, such as six months or a year. As likewise used herein, a short-term entity state 638 broadly relates to an entity state 638 that occurs for a brief interval of time, such as a few minutes or a day. In various embodiments, the method by which an entity state's 638 associated interval of time is considered to be long-term or short-term is a matter of design choice.

As an example, a particular user may have a primary work location, such as a branch office, and a secondary work location, such as their company's corporate office. In this example, the user's primary and secondary offices respectively correspond to the user's location 622, whereas the presence of the user at either office corresponds to an entity state 638. To continue the example, the user may consistently work at their primary office Monday through Thursday, but at their company's corporate office on Fridays. To further continue the example, the user's presence at their primary work location may be a long-term entity state 638, while their presence at their secondary work location may be a short-term entity state 638. Accordingly, a date/time/frequency 620 user entity behavior factor 614 can likewise be associated with user behavior respectively enacted on those days, regardless of their corresponding locations. Consequently, the long-term user entity state 638 on Monday through Thursday will typically be “working at the branch office” and the short-term entity state 638 on Friday will likely be “working at the corporate office.”

As likewise used herein, a user entity mindset profile 632 broadly refers to a collection of information that reflects an inferred mental state of a user entity at a particular time during the occurrence of an event or an enactment of a user behavior. As an example, certain information may be known about a user entity, such as their name, their title and position, and so forth, all of which are user profile attributes 612. Likewise, it may be possible to observe a user entity's associated user behavior factors 614, such as their interactions with various systems, when they log-in and log-out, when they are active at the keyboard, the rhythm of their keystrokes, and which files they typically use.

Certain embodiments of the invention reflect an appreciation these behavior factors 614 can be considered to be a behavioral fingerprint. In certain embodiments, the user behavior factors 614 may change, a little or a lot, from day to day. These changes may be benign, such as when a user entity begins a new project and accesses new data, or they may indicate something more concerning, such as a user entity who is actively preparing to steal data from their employer. In certain embodiments, the user behavior factors 614 may be implemented to ascertain the identity of a user entity. In certain embodiments, the user behavior factors 614 may be uniquely associated with a particular entity.

In certain embodiments, observed user behaviors may be used to build a user entity profile 602 for a particular user or other entity. In addition to creating a model of a user's various attributes and observed behaviors, these observations can likewise be used to infer things that are not necessarily explicit. Accordingly, in certain embodiments, a behavioral fingerprint may be used in combination with an ATP 640 to generate an inference regarding an associated user entity. As an example, a particular user may be observed eating a meal, which may or may not indicate the user is hungry. However, if it is also known that the user worked at their desk throughout lunchtime and is now eating a snack during a mid-afternoon break, then it can be inferred they are indeed hungry.

As likewise used herein, a non-user entity profile 634 broadly refers to a collection of information that uniquely describes a non-user entity's identity and its associated behavior, whether the behavior occurs within a physical realm or cyberspace. In various embodiments, the non-user entity profile 634 may be implemented to include certain non-user profile attributes 636. As used herein, a non-user profile attribute 636 broadly refers to data or metadata that can be used, individually or in combination with other non-user profile attributes 636, to ascertain the identity of a non-user entity. In various embodiments, certain non-user profile attributes 636 may be uniquely associated with a particular non-user entity.

In certain embodiments, the non-user profile attributes 636 may be implemented to include certain identity information, such as a non-user entity's network, Media Access Control (MAC), or physical address, its serial number, associated configuration information, and so forth. In various embodiments, the non-user profile attributes 636 may be implemented to include non-user behavior information associated with interactions between certain user and non-user entities, the type of those interactions, the data exchanged during the interactions, the date/time/frequency of such interactions, and certain services accessed or provided.

In certain embodiments, the ATP system 120 may be implemented to include an event enrichment 680 module, an analytic utility detection 682 module, a contextualization 684 module, a story association 686 module, and a meaning derivation 688 module, or a combination thereof. In various embodiments, the event enrichment 680 module may be implemented to perform certain event enrichment operations, described in greater detail herein. In various embodiments, the analytic utility detection 682 module may be implemented to perform certain analytic utility detection operations, as likewise described in greater detail herein.

In various embodiments, as described in greater detail herein, the contextualization 684 module may be implemented to perform certain contextualization operations. In certain embodiments, the story association 686 module may be implemented to perform story association operations, as described in greater detail herein. As likewise described in greater detail herein, the meaning derivation 688 module may be implemented in certain embodiments to perform certain meaning derivation operations. In various embodiments, the event enrichment 680 module, the analytic utility detection 682 module, the contextualization 684 module, the story association 686 module, and the meaning derivation 688 module, or a combination thereof, provide an ATP reference architecture for performing various ATP operations, described in greater detail herein.

In various embodiments, as described in greater detail herein, the ATP system 120 may be implemented to use certain data associated with an ATP 640 to derive an inference for contextualizing an electronically-observable behavior of a corresponding entity. In certain embodiments, the ATP system 120 may be implemented to use a user profile 602 in combination with a user entity mindset profile 634 and an associated entity state 638 to infer a user entity's intent. In certain embodiments, the ATP system 120 may be implemented to use various data stored in a repository of ATP data 670 to perform such an inference. In certain embodiments, the repository of ATP data 670 may include various ATPs 640 and associated contextual information, described in greater detail herein.

In various embodiments, the ATP system 120 may be implemented to use certain data associated with an ATP 640 to provide a probabilistic measure of whether a particular electronically-observable event is of analytic utility. In certain embodiments, an electronically-observable event that is of analytic utility may be determined to be anomalous, abnormal, unexpected, or malicious. To continue a prior example, a user may typically work out of their company's corporate office on Fridays. Furthermore, various mindset factors 626 within their associated user entity profile 602 may indicate that the user is typically relaxed and methodical when working with customer data. Moreover, the user's user entity profile 602 indicates that such interactions 618 with customer data typically occur on Monday mornings and the user rarely, if ever, copies or downloads customer data. However, the user may decide to interact with certain customer data late at night, on a Friday, while in their company's corporate office. As they do so, they exhibit an increased heart rate, rapid breathing, and furtive keystrokes while downloading a subset of customer data to a flash drive.

Consequently, their user entity mindset profile 632 may reflect a nervous, fearful, or guilty mindset, which is inconsistent with the entity state 638 of dealing with customer data in general. More particularly, downloading customer data late at night on a day the user is generally not in their primary office results in an entity state 638 that is likewise inconsistent with the user's typical user behavior. As a result, the ATP system 120 may infer that the user's behavior may represent a security threat. Those of skill in the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 7 is simplified block diagram of process flows associated with the operation of an adaptive trust profile (ATP) system implemented in accordance with an embodiment of the invention. In certain embodiments, the ATP system 120 may be implemented to define and manage an ATP 640, as described in greater detail herein. In certain embodiments, the ATP 640 may be implemented to comprise a user entity profile 602, likewise described in greater detail herein. In certain embodiments, the ATP system 120 may be implemented use the resulting user entity profile 602 in combination with a particular entity state 638 to generate a user entity mindset profile 632, likewise described in greater detail herein. In certain embodiments, the ATP system 120 may be implemented to use the resulting user entity mindset profile 632 in combination with an associated user entity profile 602, non-user entity profile 634, and entity state 638, or a combination thereof, to detect entity behavior of analytic utility.

In certain embodiments, the ATP system 120 may be implemented to process certain entity information associated with defining and managing an ATP 640. As used herein, entity information broadly refers to information associated with a particular entity. In various embodiments, the entity information may include certain types of content. In certain embodiments, such content may include text, unstructured data, structured data, graphical images, photographs, audio recordings, video recordings, biometric information, and so forth. In certain embodiments, the entity information may include metadata. In certain embodiments, the metadata may include entity attributes, which in turn may include certain entity identifier types or classifications.

In various embodiments, the ATP system 120 may be implemented to use certain entity identifier information to ascertain the identity of an associated entity at a particular point in time. As used herein, entity identifier information broadly refers to an information element associated with an entity that can be used to ascertain or corroborate the identity of its corresponding entity at a particular point in time. In certain embodiments, the entity identifier information may include user authentication factors, user profile attributes, user behavior factors, user mindset factors, information associated with various endpoint and edge devices, networks, resources, or a combination thereof.

In certain embodiments, the entity identifier information may include temporal information. As used herein, temporal information broadly refers to a measure of time (e.g., a date, timestamp, etc.), a measure of an interval of time (e.g., a minute, hour, day, etc.), or a measure of an interval of time (e.g., two consecutive weekdays days, or between Jun. 3, 2017 and Mar. 4, 2018, etc.). In certain embodiments, the temporal information may be associated with an event associated with a particular point in time. As used herein, such a temporal event broadly refers to an occurrence, action or activity enacted by, or associated with, an entity at a particular point in time.

Examples of such temporal events include making a phone call, sending a text or an email, using a device, such as an endpoint device, accessing a system, and entering a physical facility. Other examples of temporal events include uploading, transferring, downloading, modifying, or deleting data, such as data stored in a datastore, or accessing a service. Yet other examples of temporal events include interactions between two or more users, interactions between a user and a device, interactions between a user and a network, and interactions between a user and a resource, whether physical or otherwise. Yet still other examples of temporal events include a change in name, address, physical location, occupation, position, role, marital status, gender, association, affiliation, or assignment.

As likewise used herein, temporal event information broadly refers to temporal information associated with a particular event. In various embodiments, the temporal event information may include certain types of content. In certain embodiments, such types of content may include text, unstructured data, structured data, graphical images, photographs, audio recordings, video recordings, and so forth. In certain embodiments, the entity information may include metadata. In various embodiments, the metadata may include temporal event attributes, which in turn may include certain entity identifier types or classifications, described in greater detail herein.

In certain embodiments, the ATP system 120 may be implemented to use information associated with such temporal resolution of an entity's identity to assess the risk associated with a particular entity, at a particular point in time, and adaptively respond with an associated response. In certain embodiments, the ATP system 120 may be implemented to respond to such assessments in order to reduce operational overhead and improve system efficiency while maintaining security integrity. In certain embodiments, the response to such assessments may be performed by a security administrator. Accordingly, certain embodiments of the invention may be directed towards assessing the risk associated with the affirmative resolution of the identity of an entity at a particular point in time in combination with its associated contextual information. Consequently, the ATP system 120 may be more oriented in various embodiments to risk adaptation than to security administration.

In certain embodiments, ATP 640 definition and management operations are begun with the receipt of information associated with an initial event i 706. In certain embodiments, information associated with an initial event i 706 may include user profile attributes, user behavior factors, user mindset factors, entity state information, contextual information, described in greater detail herein, or a combination thereof. In various embodiments, certain user entity profile 602, user entity mindset profile 632, non-user entity profile 634, entity state 638 data, contextual information, and temporal information stored in a repository of ATP data 670 may be retrieved and then used to perform event enrichment 712 operations to enrich the information associated with event i 706. In certain embodiments, event enrichment 712 operations may be performed by the event enrichment module 680 of the ATP system 120 described in the text associated with FIG. 6 . Analytic utility detection 714 operations are then performed on the resulting enriched information associated with event i 706 to determine whether it is of analytic utility. In certain embodiments, the analytic utility detection 714 operations may be performed by the analytic utility detection module 682 of the ATP system 120 described in the text associated with FIG. 6 .

In various embodiments, certain contextualization information stored in the repository of ATP data 670 may be retrieved and then used to perform contextualization 716 operations to provide context, based upon the entity's user entity profile 602 or non-user entity profile 634, and its associated entity state 638. In certain embodiments, contextualization 716 operations may be performed by the contextualization module 684 of the ATP system 120, described in the text associated with FIG. 6 . In certain embodiments, a plurality of electronically-observable actions of an entity corresponding to a plurality of events enacted by an entity may be monitored, as described in greater detail herein. In various embodiments, story association 718 operations may be performed to associate certain of the plurality of electronically-observable actions of an entity with a particular story. As used herein, in the context of an ATP 640, a story broadly refers to a set of events that create a narrative that can be used to adaptively draw inferences, described in greater detail herein, regarding a particular entity. In certain embodiments, the story association 718 operations may be performed by the story association module 686 of the ATP system 120 described in the text associated with FIG. 6 .

In certain embodiments, a first plurality of electronically-observable actions of a first entity corresponding to a first plurality of events enacted by the first entity may be monitored. In turn, the first plurality of monitored events may then be associated with a story, which in certain embodiments may be used to derive an inference described in greater detail herein, regarding the first entity. In certain embodiments, a second plurality of electronically-observable actions of a second entity corresponding to a second plurality of events enacted by the second entity may be monitored. In certain embodiments, the second plurality of monitored events may then be associated with the story.

In certain embodiments, at least one of the first plurality of events enacted by the first entity may represent an interaction with the second entity. In certain embodiments, the story may be used to derive an inference regarding the interaction between the first entity and the second entity. In these embodiments, the method by which the story is used to derive an inference regarding the interaction between the first entity and the second entity is a matter of design choice.

In various embodiments, the plurality of events respectively enacted by either the first entity or the second entity may include a set of events that are of analytic utility, described in greater detail herein. In certain embodiments, the set of events that are of analytic utility may include a periodic or non-periodic sequence of events. As used herein, a sequence of events broadly refers to individual events enacted by an entity in a particular order. As an example, a user may habitually use their cell phone when first waking up in the morning to check their voicemail, followed by checking their email once they arrive at their office, followed by logging into an enterprise resource planning (ERP) system at some point thereafter.

In certain embodiments, the set of events that are of analytic utility may include events that are not sequential, yet performed on a repetitive basis, whether in part or in whole. To continue the prior example, a user may neglect to use their cell phone one morning to check their voicemail. Once in the office, they may immediately log into an ERP system to perform various tasks, followed by checking their email later in the day. To further continue the example, the user may use their cell phone the next morning to check their voicemail, followed by checking their email once they arrive in the office. However, they do not log into the ERP system. In this example, using a cell phone to check voicemail, checking email from the office, and logging into an ERP system are all events of analytic utility enacted by the user.

In certain embodiments, the set of events that are of analytic utility may include events that are not sequential, or not performed on a repetitive basis, or a combination thereof. In further continuance of the prior example, the same user may use their cellphone one morning to check their voicemail. However, instead of checking their email once they arrive at their office, or logging into the ERP system at some point during the day, the user accesses a customer relationship management (CRM) system and downloads a list of customers and their contact information. In this example, the set of events that are of analytic utility includes the absence of events that are normally performed on a repetitive basis, as well as an event that is not normally performed. Skilled practitioners of the art will recognize that many such examples of events that are of analytic utility are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In various embodiments, performance of certain story association 718 operations may result in the generation of the story. In various embodiments, performance of certain story association 718 operations may result in the generation of a plurality of stories associated with a particular entity. As an example, one story may relate to a user's interaction with one or more systems, while another story may relate to the same user's interaction with another user. Likewise, yet another story may relate to the user's interaction with a non-computing resource, such as entering or leaving a building or other venue, while yet still another story may relate to the user's interaction with various network resources. In various embodiments, performance of certain story association 718 operations may include associating certain events enacted by a given entity with a particular story associated with the entity.

In various embodiments, certain archetypal stories may be defined. In various embodiments, such predefined stories may be used to describe expected behaviors of certain classes of entities. In certain embodiments, such predefined stories may likewise be used as a starting point for the definition of an ATP 640 associated with a particular entity. In various embodiments, certain story association 718 operations may include selecting a particular story according to a set of events associated with a given entity. Those of skill in the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In certain embodiments, meaning derivation 720 operations are then performed on the stories resulting from the performance of the story association 718 operations described in greater detail herein. In certain embodiments, certain meaning derivation 718 operations may be performed by the meaning derivation module 688 of the ATP system 120 described in the text associated with FIG. 6 . In certain embodiments, the derivation of meaning may include inferring the intent of an entity associated with event i 706.

In various embodiments, performance of the meaning derivation 720 operations may result in the performance of certain risk adaptive response operations, described in greater detail herein. In various embodiments, the risk adaptive response 722 operations may include certain risk mitigation operations being performed by a security administrator. As an example, performance of the meaning derivation 720 operations may result in a notification being sent to a security administrator alerting them to the possibility of suspicious behavior. In various embodiments, the risk adaptive response 722 operations may include certain risk mitigation operations being automatically performed by a security analytics system or service. As an example, performance of the meaning derivation 720 operations may result in a user's access to a particular system being disabled if an attempted access occurs at an unusual time or from an unknown device.

In certain embodiments, meaning derivation information associated with event i 706 is then used to update the user entity profile 602 or non-user entity profile 634 corresponding to the entity associated with event i 706. In certain embodiments, the process is iteratively repeated, proceeding with meaning derivation information associated with event i+1 708 through event i+n 710. From the foregoing, skilled practitioners of the art will recognize that a user entity profile 602, or a non-user entity profile 634, or the two in combination, as implemented in certain embodiments, not only allows the identification of events associated with a particular entity that may be of analytic utility, but also provides higher-level data that allows for the contextualization of observed events. Accordingly, by viewing individual sets of events both in context and with a view to how they may be of analytic utility, it is possible to achieve a more nuanced and higher-level comprehension of an entity's intent.

FIGS. 8 a and 8 b show a block diagram of a security analytics environment implemented in accordance with an embodiment of the invention. In certain embodiments, analyses performed by a security analytics system 118 may be used to identify behavior associated with a particular entity that may be of analytic utility. In certain embodiments, the entity behavior of analytic utility may be identified at a particular point in time, during the occurrence of an event, the enactment of a user or non-user behavior, or a combination thereof.

As used herein, an entity broadly refers to something that exists as itself, whether physically or abstractly. In certain embodiments, an entity may be a user entity, a non-user entity, or a combination thereof. In certain embodiments, a user entity may be an individual user, such as user ‘A’ 802 or ‘B’ 872, a group, an organization, or a government. In certain embodiments, a non-user entity may likewise be an item, a device, such as endpoint 304 and edge 202 devices, a network, such as an internal 844 and external 846 networks, a domain, an operation, or a process. In certain embodiments, a non-user entity may be a resource 850, such as a geographical location or formation, a physical facility 852, such as a venue, various physical security devices 854, a system 856, shared devices 858, such as printer, scanner, or copier, a data store 860, or a service 862, such as a service 862 operating in a cloud environment.

As likewise used herein, an event broadly refers to the occurrence of an action performed by an entity. In certain embodiments, the action may be directly associated with a user behavior, described in greater detail herein. As an example, a first user may attach a binary file infected with a virus to an email that is subsequently sent to a second user. In this example, the act of attaching the binary file to the email is directly associated with a user behavior enacted by the first user. In certain embodiments, the action may be indirectly associated with a user behavior. To continue the example, the recipient of the email may open the infected binary file, and as a result, infect their computer with malware. To further continue the example, the act of opening the infected binary file is directly associated with a user behavior enacted by the second user. However, the infection of the email recipient's computer by the infected binary file is indirectly associated with the described user behavior enacted by the second user.

In various embodiments, certain user authentication factors 604 may be used to authenticate the identity of a user entity. In certain embodiments, the user authentication factors 604 may be used to ensure that a particular user, such as user ‘A’ 802 or ‘B’ 872, is associated with their corresponding user entity profile, rather than a user entity profile associated with another user. In certain embodiments, the user authentication factors 604 may include a user's biometrics 606 (e.g., a fingerprint or retinal scan), tokens 608 (e.g., a dongle containing cryptographic keys), user identifiers and passwords (ID/PW) 610, and personal identification numbers (PINs).

In certain embodiments, information associated with such user behavior may be stored in a user entity profile, described in greater detail herein. In certain embodiments, the user entity profile may be stored in a repository of adaptive trust profile (ATP) data 670. In certain embodiments, as likewise described in greater detail herein, the user entity profile may include user profile attributes 612, user behavior factors 614, user mindset factors 626, or a combination thereof. As used herein, a user profile attribute 612 broadly refers to data or metadata that can be used, individually or in combination with other user profile attributes 612, user behavior factors 614, or user mindset factors 626, to ascertain the identity of a user entity. In various embodiments, certain user profile attributes 612 may be uniquely associated with a particular user entity.

As likewise used herein, a user behavior factor 614 broadly refers to information associated with a user's behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, the user behavior factors 614 may include the user's access rights 616, the user's interactions 618, and the date/time/frequency 620 of those interactions 618. In certain embodiments, the user behavior factors 614 may likewise include the user's location 622 when the interactions 618 are enacted, and the user gestures 624 used to enact the interactions 618.

In various embodiments, certain date/time/frequency 620 user behavior factors 614 may be implemented as ontological or societal time, or a combination thereof. As used herein, ontological time broadly refers to how one instant in time relates to another in a chronological sense. As an example, a first user behavior enacted at 12:00 noon on May 17, 2017 may occur prior to a second user behavior enacted at 6:39 PM on May 18, 2018. Skilled practitioners of the art will recognize one value of ontological time is to determine the order in which various user behaviors have been enacted.

As likewise used herein, societal time broadly refers to the correlation of certain user profile attributes 612, user behavior factors 614, user mindset factors 626, or a combination thereof, to one or more instants in time. As an example, user ‘A’ 802 may access a particular system 856 to download a customer list at 3:47 PM on Nov. 3, 2017. Analysis of their user behavior profile indicates that it is not unusual for user ‘A’ 802 to download the customer list on a weekly basis. However, examination of their user behavior profile also indicates that user ‘A’ 802 forwarded the downloaded customer list in an email message to user ‘B’ 872 at 3:49 PM that same day. Furthermore, there is no record in their user behavior profile that user ‘A’ 802 has ever communicated with user ‘B’ 872 in the past. Moreover, it may be determined that user ‘B’ 872 is employed by a competitor. Accordingly, the correlation of user ‘A’ 806 downloading the customer list at one point in time, and then forwarding the customer list to user ‘B’ 872 at a second point in time shortly thereafter, is an example of societal time.

In a variation of the prior example, user ‘A’ 802 may download the customer list at 3:47 PM on Nov. 3, 2017. However, instead of immediately forwarding the customer list to user ‘B’ 872, user ‘A’ 802 leaves for a two week vacation. Upon their return, they forward the previously-downloaded customer list to user ‘B’ 872 at 9:14 AM on Nov. 20, 2017. From an ontological time perspective, it has been two weeks since user ‘A’ 802 accessed the system 856 to download the customer list. However, from a societal time perspective, they have still forwarded the customer list to user ‘B’ 872, despite two weeks having elapsed since the customer list was originally downloaded.

Accordingly, the correlation of user ‘A’ 802 downloading the customer list at one point in time, and then forwarding the customer list to user ‘B’ 872 at a much later point in time, is another example of societal time. More particularly, it may be inferred that the intent of user ‘A’ 802 did not change during the two weeks they were on vacation. Furthermore, user ‘A’ 802 may have attempted to mask an intended malicious act by letting some period of time elapse between the time they originally downloaded the customer list and when they eventually forwarded it to user ‘B’ 872. From the foregoing, those of skill in the art will recognize that the use of societal time may be advantageous in determining whether a particular entity behavior is of analytic utility. As used herein, mindset factors 626 broadly refer to information used to infer the mental state of a user at a particular point in time, during the occurrence of an event, an enactment of a user behavior, or combination thereof.

In certain embodiments, the security analytics system 118 may be implemented to process certain entity information, described in greater detail herein, associated with providing resolution of the identity of an entity at a particular point in time. In various embodiments, the security analytics system 118 may be implemented to use certain entity identifier information, likewise described in greater detail herein, to ascertain the identity of an associated entity at a particular point in time. In various embodiments, the entity identifier information may include certain temporal information, described in greater detail herein. In certain embodiments, the temporal information may be associated with an event associated with a particular point in time.

In certain embodiments, the security analytics system 118 may be implemented to use information associated with certain user behavior elements to resolve the identity of an entity at a particular point in time. A user behavior element, as used herein, broadly refers to a discrete element of a user entity's behavior during the performance of a particular operation in a physical realm, cyberspace, or a combination thereof. In certain embodiments, such user behavior elements may be associated with a user/device 830, a user/network 842, a user/resource 848, a user/user 860 interaction, or a combination thereof.

As an example, user ‘A’ 802 may use an endpoint device 304 to browse a particular web page on a news site on an external system 876. In this example, the individual actions performed by user ‘A’ 802 to access the web page are user behavior elements that constitute a user behavior. As another example, user ‘A’ 802 may use an endpoint device 304 to download a data file from a particular system 856. In this example, the individual actions performed by user ‘A’ 802 to download the data file, including the use of one or more user authentication factors 604 for user authentication, are user behavior elements that constitute a user behavior. In certain embodiments, the user/device 830 interactions may include an interaction between a user, such as user ‘A’ 802 or ‘B’ 872, and an endpoint device 304.

In certain embodiments, the user/device 830 interaction may include interaction with an endpoint device 304 that is not connected to a network at the time the interaction occurs. As an example, user ‘A’ 802 or ‘B’ 872 may interact with an endpoint device 304 that is offline, using applications 832, accessing data 834, or a combination thereof, it may contain. Those user/device 830 interactions, or their result, may be stored on the endpoint device 304 and then be accessed or retrieved at a later time once the endpoint device 304 is connected to the internal 844 or external 846 networks. In certain embodiments, an endpoint agent 306 may be implemented to store the user/device 830 interactions when the user device 304 is offline.

In certain embodiments, an endpoint device 304 may be implemented with a device camera 828. In certain embodiments, the device camera 828 may be integrated into the endpoint device 304. In certain embodiments, the device camera 828 may be implemented as a separate device configured to interoperate with the endpoint device 304. As an example, a webcam familiar to those of skill in the art may be implemented receive and communicate various image and audio signals to an endpoint device 304 via a Universal Serial Bus (USB) interface.

In certain embodiments, the device camera 828 may be implemented to capture and provide user/device 830 interaction information to an endpoint agent 306. In various embodiments, the device camera 828 may be implemented to provide surveillance information related to certain user/device 830 or user/user 870 interactions. In certain embodiments, the surveillance information may be used by the security analytics system 118 to detect behavior associated with a user entity, such as user ‘A’ 802 or user ‘B’ 872 that may be of analytic utility.

In certain embodiments, the endpoint device 304 may be used to communicate data through the use of an internal network 844, an external network 846, or a combination thereof. In certain embodiments, the internal 844 and the external 846 networks may include a public network, such as the Internet, a physical private network, a virtual private network (VPN), or any combination thereof. In certain embodiments, the internal 844 and external 846 networks may likewise include a wireless network, including a personal area network (PAN), based on technologies such as Bluetooth. In various embodiments, the wireless network may include a wireless local area network (WLAN), based on variations of the IEEE 802.11 specification, commonly referred to as WiFi. In certain embodiments, the wireless network may include a wireless wide area network (WWAN) based on an industry standard including various 3G, 4G and 5G technologies.

In certain embodiments, the user/user 870 interactions may include interactions between two or more user entities, such as user ‘A’ 802 and ‘B’ 872. In certain embodiments, the user/user interactions 870 may be physical, such as a face-to-face meeting, via a user/device 830 interaction, a user/network 842 interaction, a user/resource 648 interaction, or some combination thereof. In certain embodiments, the user/user 870 interaction may include a face-to-face verbal exchange. In certain embodiments, the user/user 870 interaction may include a written exchange, such as text written on a sheet of paper. In certain embodiments, the user/user 870 interaction may include a face-to-face exchange of gestures, such as a sign language exchange.

In certain embodiments, temporal event information associated with various user/device 830, user/network 842, user/resource 848, or user/user 870 interactions may be collected and used to provide real-time resolution of the identity of an entity at a particular point in time. Those of skill in the art will recognize that many such examples of user/device 830, user/network 842, user/resource 848, and user/user 870 interactions are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In various embodiments, the security analytics system 118 may be implemented to process certain contextual information in the performance of certain security analytic operations. As used herein, contextual information broadly refers to any information, directly or indirectly, individually or in combination, related to a particular entity behavior. In certain embodiments, entity behavior may include a user entity's physical behavior, cyber behavior, or a combination thereof. As likewise used herein, a user entity's physical behavior broadly refers to any user behavior occurring within a physical realm, such as speaking, gesturing, facial patterns or expressions, walking, and so forth. More particularly, such physical behavior may include any action enacted by an entity user that can be objectively observed, or indirectly inferred, within a physical realm. In certain embodiments, the objective observation, or indirect inference, of the physical behavior may be performed electronically.

As an example, a user may attempt to use an electronic access card to enter a secured building at a certain time. In this example, the use of the access card to enter the building is the action and the reading of the access card makes the user's physical behavior electronically-observable. As another example, a first user may physically transfer a document to a second user, which is captured by a video surveillance system. In this example, the physical transferal of the document from the first user to the second user is the action. Likewise, the video record of the transferal makes the first and second user's physical behavior electronically-observable. As used herein, electronically-observable user behavior broadly refers to any behavior exhibited or enacted by a user entity that can be observed through the use of an electronic device (e.g., an electronic sensor), a computing device or system (e.g., an endpoint 304 or edge 202 device, a physical security device 854, a system 856, a shared device 858, etc.), computer instructions (e.g., a software application), or a combination thereof.

Cyber behavior, as used herein, broadly refers to any behavior occurring in cyberspace, whether enacted by an individual user, a group of users, or a system acting at the behest of an individual user, a group of users, or other entity. More particularly, cyber behavior may include physical, social, or mental actions that can be objectively observed, or indirectly inferred, within cyberspace. As an example, a user may use an endpoint device 304 to access and browse a particular website on the Internet. In this example, the individual actions performed by the user to access and browse the website constitute a cyber behavior. As another example, a user may use an endpoint device 304 to download a data file from a particular system 856 at a particular point in time. In this example, the individual actions performed by the user to download the data file, and associated temporal information, such as a time-stamp associated with the download, constitute a cyber behavior. In these examples, the actions are enacted within cyberspace, in combination with associated temporal information, which makes them electronically-observable.

In certain embodiments, the contextual information may include location data 836. In certain embodiments, the endpoint device 304 may be configured to receive such location data 836, which is used as a data source for determining the user's location 622. In certain embodiments, the location data 836 may include Global Positioning System (GPS) data provided by a GPS satellite 838. In certain embodiments, the location data 836 may include location data 836 provided by a wireless network, such as from a cellular network tower 840. In certain embodiments (not shown), the location data 836 may include various Internet Protocol (IP) or other network address information assigned to the endpoint 304 or edge 202 device. In certain embodiments (also not shown), the location data 836 may include recognizable structures or physical addresses within a digital image or video recording.

In certain embodiments, the endpoint devices 304 may include an input device (not shown), such as a keypad, magnetic card reader, token interface, biometric sensor, and so forth. In certain embodiments, such endpoint devices 304 may be directly, or indirectly, connected to a particular facility 852, physical security device 854, system 856, or shared device 858. As an example, the endpoint device 304 may be directly connected to an ingress/egress system, such as an electronic lock on a door or an access gate of a parking garage. As another example, the endpoint device 304 may be indirectly connected to a physical security device 854 through a dedicated security network.

In certain embodiments, the security analytics system 118 may be implemented to perform various risk-adaptive protection operations. Risk-adaptive, as used herein, broadly refers to adaptively responding to risks associated with an electronically-observable entity behavior. In various embodiments, the security analytics system 118 may be implemented to perform certain risk-adaptive protection operations by monitoring certain entity behaviors, assess the corresponding risk they may represent, individually or in combination, and respond with an associated response. In certain embodiments, such responses may be based upon contextual information, described in greater detail herein, associated with a given entity behavior.

In certain embodiments, various risk-adaptive behavior factors 674, likewise described in greater detail herein, may be used to perform the risk-adaptive protection operations. In certain embodiments, the risk-adaptive behavior factors 674 may include user profile attributes 612, user behavior factors 614, user mindset factors 626, or a combination thereof. In these embodiments, the risk-adaptive behavior factors 674 used to perform the risk-adaptive protection operations is a matter of design choice.

In certain embodiments, the security analytics system 118 may be implemented as a stand-alone system. In certain embodiments, the security analytics system 118 may be implemented as a distributed system. In certain embodiment, the security analytics system 118 may be implemented as a virtual system, such as an instantiation of one or more virtual machines (VMs). In certain embodiments, the security analytics system 118 may be implemented as a security analytics service 864. In certain embodiments, the security analytics service 864 may be implemented in a cloud environment familiar to those of skill in the art. In various embodiments, the security analytics system 118 may use data stored in a repository of security analytics data 880 in the performance of certain security analytics operations, described in greater detail herein. Those of skill in the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 9 shows a functional block diagram of an adaptive trust profile (ATP) system implemented in accordance with an embodiment of the invention. In various embodiments, certain ATP-related information, described in greater detail herein, may be provided by endpoint devices 304, edge devices 202, and third party sources 906. In certain embodiments, the receipt of ATP information provided by third party sources 906 may be facilitated through the implementation of one or more Apache NiFi connectors 908, familiar to skilled practitioners of the art. In certain embodiments, sessionalization operations are performed in block 910 on the ATP-related information provided by the endpoint devices 304, edge devices 202, and third party sources 906 to generate discrete sessions. In these embodiments, the method by which ATP-related information is selected to be used in the generation of a particular session, and the method by which the session is generated, is a matter of design choice.

As used herein, a session broadly refers to an interval of time during which one or more user or non-user behaviors are respectively enacted by a user or non-user entity. In certain embodiments, the user or non-user behaviors enacted during a session may be respectively associated with one or more events, described in greater detail herein. In certain embodiments, a session may be implemented to determine whether or not user or non-user behaviors enacted during the session are of analytic utility. As an example, certain user or non-user behaviors enacted during a particular session may indicate the behaviors were enacted by an impostor. As another example, certain user or non-user behaviors enacted during a particular session may be performed by an authenticated entity, but the behaviors may be unexpected or out of the norm.

In certain embodiments, two or more sessions may be contiguous. In certain embodiments, two or more sessions may be noncontiguous, but associated. In certain embodiments, a session may be associated with two or more other sessions. In certain embodiments, a session may be a subset of another session. In certain embodiments, the interval of time corresponding to a first session may overlap an interval of time corresponding to a second session. In certain embodiments, a session may be associated with two or more other sessions whose associated intervals of time may overlap one another. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

The resulting sessions are then ingested in block 916, followed by the performance of data enrichment operations familiar to those of skill in the art in block 914. In certain embodiments, user identifier information (ID) information provided by a user ID management system 912 may be used in block 914 to perform the data enrichment operations. In various embodiments, certain contextual information related to a particular entity behavior or event may be used in block 914 to perform the data enrichment operations. In various embodiments, certain temporal information, such as timestamp information, related to a particular entity behavior or event may be used in block 914 to perform the data enrichment operations. In certain embodiments, a repository of ATP data 970 may be implemented to include repositories of entity attribute data 920 and behavioral model data 924. In various embodiments, certain information stored in the repository of entity attribute data 920 may be used to perform the data enrichment operations in block 914.

In certain embodiments, the resulting enriched sessions may be stored in a repository of raw event data 918. In certain embodiments, the resulting enriched sessions may be provided to a risk services 422 module, described in greater detail herein. In certain embodiments, as likewise described in greater detail herein, the risk services 422 module may be implemented to generate inferences, risk models, and risk scores, or a combination thereof. In certain embodiments, the resulting inferences, risk models, or risk scores may then be stored in the repository of behavioral model data.

In certain embodiments, the risk services 422 module may be implemented to provide input data associated with the inferences, risk models, and risk scores it may generate to a policy service 928. In certain embodiments, the policy service 928 may be implemented to use the inferences, risk models, and risk scores to generate policies. In turn, the policy service 928 may be implemented in certain embodiments to export the resulting policies to endpoint agents, edge devices, or other security mechanisms, where they may be used to limit risk, as described in greater detail herein. In certain embodiments, a user interface (UI) or front-end 926 familiar to skilled practitioners of the art may be implemented to provide administrative access to various components of the ATP system 120, as shown in FIG. 9 .

FIG. 10 is a table showing components of an adaptive trust profile (ATP) implemented in accordance with an embodiment of the invention. In various embodiments, an ATP 640 may be implemented to certain include entity attributes 1004, behavioral models 1006, and inferences 1008, along with entity state 638. In certain embodiments, an ATP's 640 entity state 638 may be short-term, or reflect the state of an entity at a particular point or interval in time. In certain embodiments, an ATP's 640 entity state 638 may be long-term, or reflect the state of an entity at recurring points or intervals in time.

In certain embodiments, an ATP's 640 associated entity attributes 1004 may be long-lived. As an example, a particular user entity may have a name, an employee ID, an assigned office, and so forth, all of which are facts rather than insights. In certain embodiments, a particular entity state 638 may be sufficiently long-termed to be considered an entity attribute 1004. As an example, a first user and a second user may both have an entity state 638 of being irritable. However, the first user may have a short-term entity state 638 of being irritable on an infrequent basis, while the second user may have a long-term entity state 638 of be irritable on a recurring basis. In this example, the long-term entity state 638 of the second user being irritable may be considered to be an entity attribute. In various embodiments, the determination of what constitutes an entity state 638 and an entity attribute 1004 is a matter of design choice. In certain embodiments, various knowledge representation approaches may be implemented in combination with an ATP system to understand the ontological interrelationship of entity attributes 1004 one or more ATP's 640 may contain. In these embodiments, the method by which certain entity attributes 1004 are selected to be tracked by an ATP system, and the method by which they are managed within a corresponding ATP 640, is a matter of design choice.

In certain embodiments, the ATP 640 evolves over time as new events and entity behavior is detected. In certain embodiments, an ATP's 640 associated behavioral models 1006, and thus the ATP 640 itself may evolve over time. In certain embodiments, an ATP's 640 behavioral models 1006 may be used by an ATP system to provide insight into how unexpected a set of events may be. As an example, a behavioral model 1006 may include information related to where a particular user entity works, which devices they may use and locations they may login from, who they may communicate with, and so forth. Certain embodiments of the invention reflect an appreciation that such behavioral models 1006 can be useful when comparing observe user and non-user behaviors to past observations in order to determine how unusual a particular action may be.

For example, a user may have more than one ATP 640 associated with a particular channel, which as used herein broadly refers to a medium capable of supporting the electronic observation of a user or non-user behavior, such as a keyboard, a network, a video stream, and so forth. To continue the example, the user may have a particular set of people he sends emails to from his desktop computer, and does so in an orderly and methodical manner, carefully choosing his words, and writing longer than average messages compared to his peers. Consequently, analysis of such an email message will likely indicate it was authored by the user and not someone else.

However, the same user may also send emails from a second channel, which is his mobile telephone. When using his mobile telephone, the user's emails are typically short, contains typos and emojis, and his writing style is primarily limited to simple confirmations or denials. Consequently, analysis of one such email would likely not reveal whether the user was the author or not, due to its brevity. Accordingly, the use of the same channel, which in this example is email, demonstrates the use of different devices will likely generate different behavioural models 1006, which in turn could affect the veracity of associated inferences 1008.

In certain embodiments, a behavioral model 1006 may be implemented as a session-based fingerprint. As used herein, a session-based fingerprint broadly refers to a unique identifier of an enactor of user or non-user behavior associated with a session. In certain embodiments, the session-based fingerprint may be implemented to determine how unexpected an event may be, based upon an entity's history as it relates to the respective history of their peer entities. In certain embodiments, the session-based fingerprint may be implemented to determine whether an entity associated with a particular session is truly who they or it claims to be or if they are being impersonated. In certain embodiments, the session-based fingerprint may be implemented to determine whether a particular event, or a combination thereof, may be of analytic utility. In certain embodiments, the session-based fingerprint may include a risk score, be used to generate a risk score, or a combination thereof.

As likewise used herein, a fingerprint, as it relates to a session, broadly refers to a collection of information providing one or more distinctive, characteristic indicators of the identity of an enactor of one or more corresponding user or non-user entity behaviors during the session. In certain embodiments, the collection of information may include one or more user or non-user profile elements. A user or non-user profile element, as used herein, broadly refers to a collection of user or non-user entity behavior elements, described in greater detail herein.

As used herein, inferences 1008 broadly refer to things that can be inferred about an entity based upon observations. In certain embodiments the observations may be based upon electronically-observable behavior, described in greater detail herein. In certain embodiments, the behavior may be enacted by a user entity, a non-user entity, or a combination thereof. In certain embodiments, inferences 1008 may be used to provide insight into a user entity's mindset or affective state.

As an example, an inference 1008 may be made that a user is unhappy in their job or that they are facing significant personal financial pressures. Likewise, based upon the user's observed behavior, an inference 1008 may be made that they are at a higher risk of being victimized by phishing schemes due to a propensity for clicking on random or risky website links. In certain embodiments, such inferences 1008 may be implemented to generate a predictive quantifier of risk associated with an entity's behavior.

In certain embodiments, entity state 638, described in greater detail herein, may be implemented such that changes in state can be accommodated quickly while reducing the overall volatility of a particular ATP 640. As an example, a user may be traveling by automobile. Accordingly, the user's location is changing quickly. Consequently, location data is short-lived. As a result, while the location of the user may not be updated within their associated ATP 640 as it changes, the fact their location is changing may prove to be useful in terms of interpreting other location-based data from other sessions. To continue the example, knowing the user is in the process of changing their location may assist in explaining why the user appears to be in two physical locations at once.

FIG. 11 is a table showing analytic utility actions occurring during a session implemented in accordance with an embodiment of the invention. In certain embodiments, an adaptive trust profile (ATP) system, described in greater detail herein, may be implemented to capture and record various actions 1104 enacted by an entity during a session 1102, likewise described in greater detail herein. In certain embodiments, the actions, and their associated sessions, may be stored in an ATP corresponding to a particular entity. In various embodiments, the ATP system may be implemented to process information stored in an ATP to determine, as described in greater detail herein, which actions 1104 enacted by a corresponding entity during a particular session 1102 may be of analytic utility 1108.

Certain embodiments of the invention reflect an appreciation that multiple sessions 1102, each of which may be respectively associated with a corresponding entity, may occur within the same interval of time 1106. Certain embodiments of the invention likewise reflect an appreciation that a single action of analytic utility 1108 enacted by an entity occurring during a particular interval of time 1106 may not appear to be suspicious behavior by an associated entity. Likewise, certain embodiments of the invention reflect an appreciation that the occurrence of multiple actions of analytic utility 1108 enacted by an entity during a particular session 1102 may be an indicator of suspicious behavior.

Certain embodiments reflect an appreciation that a particular entity may be associated with two or more sessions 1102 that occur concurrently over a period of time 1106. Certain embodiments of the invention likewise reflect an appreciation that a single action of analytic utility 1108 enacted by an entity occurring during a first session 1102 may not appear to be suspicious. Conversely, certain embodiments of the invention reflect an appreciation that multiple actions of analytic utility 1108 during a second session 1102 may.

As an example, a user may log into the same system from two different IP addresses, one associated with their laptop computer and the other their mobile phone. In this example, actions 1104 enacted by the user using their laptop computer may be associated with a first session 1102 (e.g. session ‘2’), and actions 1104 enacted by the user using their mobile phone may be associated with a second session 1102 (e.g., session ‘3’). To continue the example, only one action of analytic utility 1108 may be associated with the first session 1102, while three actions of analytic utility 1108 may be associated with the second session 1102. Accordingly, it may be inferred the preponderance of actions of analytic utility 1108 enacted by the user during the second session 1102 may indicate suspicious behavior being enacted with their mobile phone.

FIG. 12 is a simplified block diagram of an adaptive trust profile (ATP) system environment implemented in accordance with an embodiment of the invention. In certain embodiments, the ATP system environment may be implemented to detect user or non-user entity behavior of analytic utility and adaptively respond to mitigate risk. In certain embodiments, the ATP system environment may be implemented to include a security analytics system 118. In certain embodiments, the security analytics system 118 may be implemented to include an ATP system 120.

In certain embodiments, the ATP system 120, as described in greater detail herein, may be implemented to use session-based security information to generate an ATP, likewise describe in greater detail herein. As used herein, session-based security information broadly refers to any information associated with a session that can be used to detect entity behavior of analytic utility and mitigate its associated risk. In certain embodiments, the session-based security information may include a session-based fingerprint, described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented to use one or more session-based fingerprints to perform security analytics operations to detect such user or non-user entity behavior. In certain embodiments, the security analytics system 118 may be implemented to monitor user behavior associated with a user entity, such as a user 802. In certain embodiments, the user or non-user entity behavior is monitored during user/device 830, user/network 842, user/resource 848, and user/user 860 interactions. In certain embodiments, the user/user 860 interactions may occur between a first user, such as a first user 802 and a second user 802.

In certain embodiments, as described in greater detail herein, an endpoint agent 306 may be implemented on the endpoint device 304 to perform user or non-user entity behavior monitoring. In certain embodiments, the user or non-user entity behavior may be monitored by the endpoint agent 306 during user/device 830 interactions between a user entity, such as a user 802, and an endpoint device 304. In certain embodiments, the user or non-user entity behavior may be monitored by the endpoint agent 306 during user/network 842 interactions between user ‘A’ 902 and a network, such as an internal 844 or external 846 network. In certain embodiments, the monitoring of user or non-user entity behavior by the endpoint agent 306 may include the monitoring of electronically-observable actions respectively enacted by a particular user or non-user entity. In certain embodiments, the endpoint agent 306 may be implemented in combination with the security analytics system 118 and the ATP system 120 to detect entity behavior of analytic utility and adaptively respond to mitigate risk.

In certain embodiments, the endpoint agent 306 may be implemented to include an analytics 310 module and an ATP feature pack 1208. In certain embodiments, the ATP feature pack 1208 may be further implemented to include an event data detector 1210 module, an entity behavior detector 1212 module, and a session correlation 1214 module. In certain embodiments, the event data detector 1210 module may be implemented to detect event data, described in greater detail herein, resulting from user/device 830, user/network 842, user/resource 848, and user/user 860 interactions. In various embodiments, the entity behavior detector 1212 module may be implemented to detect certain user and non-user entity behaviors, described in greater detail herein, resulting from user/device 830, user/network 842, user/resource 848, and user/user 860 interactions.

In various embodiments, the session correlation 1214 module may be implemented to generate session data by correlating certain event behavior data detected by the event data detector 1210 module with a particular session. In various embodiments, the session correlation 1214 module may be implemented to generate session data by correlating certain user and non-user entity behavior data detected by the entity behavior detector 1212 module with a particular session. In certain embodiments, the endpoint agent 306 may be implemented to communicate the event data detected by the event data detector 1210 module, the user and non-user entity behavior data detected by the entity behavior detector 1212 module, the session data generated by the session data detector 1214 module, or a combination thereof, to the security analytics 118 system.

In certain embodiments, the security analytics system 118 may be implemented to receive the event data, the user and non-user entity behavior data, and the session data provided by the endpoint agent 306. In certain embodiments, the security analytics system 118 may be implemented to provide the event data, the user and non-user entity behavior data, and the session data to the ATP system 120 for processing. In certain embodiment, the ATP system 120 may be implemented to include an ATP element collector 1282 module, an ATP element analytics 1284 module, a session generator 1286 module, a session-based fingerprint generator 1288 module, an ATP generator 1290 module, or a combination thereof.

In certain embodiments, the ATP element collector 1282 module may be implemented to process the event data, the user and non-user entity behavior data, and the session data provided by the endpoint agent 306 to generate ATP elements, described in greater detail herein. In various embodiments, the ATP element analytics 1284 module may be implemented to analyze certain ATP elements to detect possible user or non-user entity behavior of analytic utility associated with a particular event. In certain embodiments, the ATP session generator 1286 module may be implemented to process the ATP elements collected by the ATP element collector 1282 module to generate one or more associated sessions. In certain embodiments, the session-based fingerprint generator 1288 module may be implemented to process the sessions generated by the session generator 1286 module to generate one or more session-based fingerprints. In certain embodiments, the ATP generator 1290 module may be implemented to process the sessions generated by the ATP session generator 1286 module, the session-based fingerprints generated by the session-based fingerprint generator 1288 module, or a combination thereof, to generate am ATP profile, as described in greater detail herein.

FIG. 13 is a generalized flowchart of session-based fingerprint generation operations performed in accordance with an embodiment of the invention. In this embodiment, session-based fingerprint generation operations are begun in step 1302, followed by the selection of an entity in step 1304 for associated adaptive trust profile (ATP) element generation. As used herein, an ATP element broadly refers to any data element stored in an ATP, as described in greater detail herein. Ongoing monitoring operations are then performed in step 1306 to entity behavior data associated with the entity selected in step 1304.

A determination is then made in step 1308 whether entity behavior data has been detected. If not, then a determination is made in step 1326 whether to continue monitoring the entity's behavior to detect associated entity behavior data. If so, then the process is continued, proceeding with step 1306. Otherwise, session-based fingerprint generation operations are ended in step 1328. However, if it was determined in step 1308 that entity behavior data was detected, then the detected entity data is processed in step 1310 to generate an associated ATP element.

A determination is then made in step 1312 whether to generate a new ATP for the entity. If not, then a target ATP associated with the entity is selected in step 1314. Otherwise, a new ATP for the entity is generated in step 1316. Thereafter, or once a target ATP associated with the entity has been selected in step 1315, the previously-generated ATP element is added to the selected or newly-generated ATP in step 1318.

The ATP elements within the ATP are then processed in step 1320 to generate a session, described in greater detail herein. The resulting session is in turn processed in step 1322 to generate a corresponding session-based fingerprint. The session and its corresponding session-based fingerprint are then associated with the ATP in step 1324 that is likewise associated with the entity. The process is then continued, proceeding with step 1326.

FIGS. 14 a and 14 b are a generalized flowchart of the performance of adaptive trust profile (ATP) definition and management operations implemented in accordance with an embodiment of the invention. In this embodiment, ATP definition and management operations are begun in step 1402, followed by ongoing operations being performed by an ATP system in step 1404 to ATP elements, as described in greater detail herein. A determination is then made in step 1406 whether an ATP element has been received by the ATP system.

If not, then a determination is made in step 1436 to determine whether to continue monitoring for ATP elements. If so, then the process is continued, proceeding with step 1404. Otherwise, a determination is made in step 1438 whether to end transportable cyberprofile generation operations. If not, then the process is continued, proceeding with step 1404. Otherwise, ATP definition and management operations are ended in step 1438.

However, if it was determined in step 1406 that an ATP element was received, then it is processed in step 1408 to determine its associated entity. A determination is then made in step 1410 whether to generate a new ATP for the entity. If not, then an ATP associated with the entity is selected in step 1412 and then updated with the ATP element in step 1414. However, if it was determined in step 1410 to generate a new ATP for the entity, then it is generated in step 1416 and populated with the ATP element in step 1418.

Thereafter, or after the selected ATP is updated in step 1414, the ATP is processed in step 1420 to perform data enrichment operations, described in greater detail herein. Analytic utility detection operations, likewise described in greater detail herein, are then performed on the enriched ATP in step 1422 to identify entity behavior that may be of analytic utility. Thereafter, a determination is made in step 1424 to determine whether the entity behavior is of analytic utility. If not, then a determination is made in step 1434 whether to continue ATP definition and management operations. If so, then the process is continued, proceeding with step 1404. Otherwise, ATP definition and management operations are ended in step 1438.

However, if it was determined in step 1424 that the entity behavior was of analytic utility, the contextual information is retrieved in step 1426 and then processed in step 1428 with entity attributes stored in the ATP with a behavioral model to generate one or more inferences, described in greater detail herein. A determination is then made in step 1430 whether the one or more inferences indicate behavior by the entity is of analytic utility. If not, the process is continued, proceeding with step 1434. Otherwise, appropriate risk mitigation operations are performed in step 1432 and the process is then continued, proceeding with step 1434.

FIG. 15 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention to adaptively assess risk associated with an entity behavior. In this embodiment, entity behavior is monitored and compared to known good behavior 1502 and known bad behavior 1504. In typical risk assessment 1506 approaches, low 1508, moderate 1510, or high 1512 risk entity behavior is generally determined by using fairly inflexible security policies, which are typically used to enact relatively static responses.

As an example, a security policy implemented for access control may have a list of actions a particular entity can do and a list of things they cannot. Ordinarily, the actions in those lists are static and don't change, regardless of the particular entity behavior being enacted. However, perhaps they should change, or adapt, if it is determined the entity behavior being enacted by the entity has changed, and as a result, represents a higher risk

To continue the example, a user may be perusing various resources and happens to access a webpage, such as a shopping site, that contains certain objects. Typical security approaches assume some portion of those objects to be good, a small number are known to be bad, and the remainder suspicious. Consequently, there is a continuum of objects, some assumed to be good, some undetermined, and the rest known to be bad. It will be appreciated that the determination of what is considered to be good, undetermined, or bad is oftentimes fairly arbitrary.

In certain embodiments, contextual information associated with the entity behavior is collected and processed to adaptively respond to changes in the entity's current behavior. In continuance of the example, the user may change their behavior to access internal business resources. In this example, accessing internal business resources is contextual information that may represent the potential for higher risk. As a result, a risk-adaptive behavior system may be implemented in certain embodiments to respond with an adaptive high risk assessment 1514. In certain embodiments, the adaptive high risk assessment 1514 is generated by a security analytics system, described in greater detail herein. Consequently, the adaptive high risk assessment 1514 may indicate a larger percentage of certain entity behavior as high 1520 risk, and a smaller percentage as low 1516 or moderate 1518 risk.

In further continuance of the example, the user may further change their behavior to access an external news site. As before, the user's access of an external news site is contextual information that may represent the likelihood of lower risk. As a result, the risk-adaptive behavior system may be implemented to respond with an adaptive low risk assessment 1522, which may indicate a larger percentage of certain entity behavior as low 1524 risk, and a smaller percentage as moderate 1526 or high 1528 risk.

Certain embodiments of the invention reflect an appreciation that without the described adaptive behavior, the operational overhead administering entity security would be high, as all entity interactions related to their behavior would continue to be monitored. However, the cost of administering entity security would decrease when the entity was no longer interacting with internal resources. Consequently, risk tolerance can be dynamically adjusted according to the context of a given entity activity.

More particularly, if the entity's activity is primarily internal to the organization, then some risk can be tolerated. However, if the entity's activity is primarily external to the organization, then it is possible that essentially all risk can be tolerated. Furthermore, the user experience may be more pleasant during non-organization activities, as fewer security controls may be applied or experienced. Moreover, the risk assessment becomes dynamic, according to the identity of the entity, the resources being accessed, their respective behavior, and corresponding points of observation.

FIG. 16 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention to adaptively respond to an entity request. In this embodiment, an entity may place a request 1606 to download a file from a file source 1608 to a file destination 1604, such as a USB drive. In traditional security approaches, the owner of the requested file may have a single security rule, which would be a granted 1612, or denied 1614, request response 1610 as to whether the entity was allowed to download the file.

In certain embodiments, a risk-adaptive security policy may be implemented such that the entity's request 1606 to download the requested file is typically granted 1612. However, as an example, a user may have recently updated their online resume as well as begun to take random days off, which may imply a flight risk. By extension, the user behavior and other actions associated with the user may likewise imply the user's intent to take proprietary information with them to a new job. Consequently, various risk-adaptive behavior approaches may yield a denied 1614 request response 1610 due to the associated context of their behavior, other actions, or a combination thereof.

Alternatively, a risk-adaptive security policy may be implemented in various embodiments to provide a conditional 1616 request response 1610. As an example, a requested file may be encrypted such that it can only be opened on a corporate computer. Furthermore, attempting to open the file on a non-corporate computer may result in a message being sent to a security administrator. Likewise, a single file being downloaded may appear as good behavior, yet multiple sequential downloads may appear suspicious, especially if the files do not appear to be related, or possibly, if they do. From the foregoing, it will be appreciated that risk-adaptive behavior is not necessarily based upon an atomic action, but rather a multiplicity of factors, such as contextual information associated with particular entity behavior.

FIG. 17 is a generalized flowchart of the performance of security analytics system operations implemented in accordance with an embodiment of the invention to adaptively manage entity behavior risk. In this embodiment, risk-adaptive behavior operations are begun in step 1702, followed by the performance of entity authentication operations, familiar to those of skill in the art, in step 1704. A determination is then made in step 1706 whether the entity has one or more associated risk-adaptive security policies. If so, then they are retrieved for use in step 1708. Thereafter, or if it was determined in step 1706 the entity has no associated risk-adaptive security policies, the entity's behavior is monitored in step 1710.

The entity's current user behavior is then processed in step 1712 to identify any applicable risk-adaptive security policies that may apply. A determination is then made in step 1714 whether any applicable risk-adaptive security policies have been identified. If not, a determination is made in step 1726 whether to end risk-adaptive behavior system operations. If not, then the process is continued, proceeding with step 1710. Otherwise, risk-adaptive behavior system operations are ended in step 1728.

However, if it is determined in step 1714 that one or more applicable risk-adaptive security policies have been identified, then they are used in step 1716 to process the entity's current user behavior to determine an appropriate risk-adaptive behavior response. The appropriate risk-adaptive behavior response is then enacted in step 1718, followed by a determination being made in step 1720 whether the risk-adaptive behavior response enacted in step 1718 indicates acceptable user behavior.

If so, then the process is continued, proceeding with step 1726. Otherwise the entity's current behavior is determined to be of analytic utility and marked accordingly in step 1722. Entity behavior of analytic utility notification operations are then performed in step 1724. In one embodiment, entity behavior of analytic utility is stored for later review. In another embodiment, a security administrator is notified of the enactment of entity behavior of analytic utility. Thereafter, the process is continued, proceeding with step 1726.

FIG. 18 is a generalized flowchart of the performance of story association operations implemented in accordance with an embodiment of the invention. In this embodiment, story association operations are begun in step 1802, followed by the receipt of information associated with an event enacted by a particular entity in step 1804. Temporal and other information associated with the event is then retrieved in step 1806, followed by the retrieval of an adaptive trust profile (ATP) associated with the entity in step 1808. The retrieved temporal and other information is then used in step 1810, as described in greater detail herein, to enrich the information associated with the event.

A determination is then made in step 1812 whether the event is of analytic utility, as likewise described in greater detail herein. If not, then a determination is made in step 1826 whether to end story association operations. If not, then the process is continued, proceeding with step 1804. Otherwise, story association operations are ended in step 1828. However, if it was determined in step 1812 that the event is of analytic utility, the event contextualization operations, described in greater detail herein, are performed in step 1814.

A story, described in greater detail herein, associated with the entity is then selected in step 1816, followed by the performance of story association operations, likewise described in greater detail herein, in step 1818 to associate the enriched and contexualized event with the previously selected story. Meaning derivation operations, as described in greater detail herein, are then performed on the story in step 1820, followed by a determination being made in step 1822 whether the meaning derived in step 1820 warrants an adaptive response. If so, then an adaptive response operation, likewise described in greater detail herein, is performed in step 1824. Thereafter, or if it was determined in step 1822 not to perform an adaptive response operation, the process is continued, proceeding with step 1826.

As will be appreciated by one skilled in the art, the present invention may be embodied as a method, system, or computer program product. Accordingly, embodiments of the invention may be implemented entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in an embodiment combining software and hardware. These various embodiments may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Embodiments of the invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this invention and its broader aspects. Therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those with skill in the art that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation no such limitation is present. For non-limiting example, as an aid to understanding, the following appended claims contain usage of the introductory phrases “at least one” and “one or more” to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an”; the same holds true for the use in the claims of definite articles.

The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.

Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects. 

1-20. (canceled)
 21. A computer-implementable method for generating and managing an adaptive trust profile, comprising: monitoring a plurality of electronically-observable actions of an entity, the plurality of electronically-observable actions of the entity corresponding to a respective plurality of events enacted by the entity, the entity comprising a user entity; generating the adaptive trust profile based upon the plurality of actions of the entity, the adaptive trust profile being generated by an adaptive trust profile system, the adaptive trust profile comprising a collection of information describing an identity of the entity, the adaptive trust profile system executing on a hardware processor of an information handling system; determining, via the adaptive trust profile system, whether an event of the plurality of events enacted by the entity is of analytic utility, the event being of analytic utility indicating an entity behavior associated with the event represents a security risk; generating, via the adaptive trust profile system, contextual information about the event based upon an entity profile, the contextual information comprising information relating to a particular entity behavior; deriving, via the adaptive trust profile system, a meaning from the contextual information associated with the event, the meaning including an inference of an intent of the entity associated with the event; and, updating, via the adaptive trust profile system, the adaptive trust profile of the entity based upon the contextual information about the event and the intent of the entity associated with the event.
 22. The method of claim 21, wherein: the adaptive trust profile system comprises an event enrichment module, the event enrichment module performing an event enrichment operation.
 23. The method of claim 21, wherein: the adaptive trust profile system comprises a meaning derivation module, the meaning derivation module performing a meaning derivation operation, the meaning derivation operation deriving the meaning from the contextualized information.
 24. The method of claim 21, wherein: the adaptive trust profile system comprises a contextualization module, the contextualization module performing a contextualization operation, the contextualization operation generating the contextual information.
 25. The method of claim 21, wherein: the adaptive trust profile system comprises an anomaly detection module, the anomaly detection module performing an anomaly detection operation.
 26. The method of claim 25, wherein: the anomaly detection operation determines whether the event of the plurality of events is of analytic utility.
 27. A system comprising: a hardware processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code for generating and managing an adaptive trust profile, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: monitoring a plurality of electronically-observable actions of an entity, the plurality of electronically-observable actions of the entity corresponding to a respective plurality of events enacted by the entity, the entity comprising a user entity; generating the adaptive trust profile based upon the plurality of actions of the entity, the adaptive trust profile being generated by an adaptive trust profile system, the adaptive trust profile comprising a collection of information describing an identity of the entity, the adaptive trust profile system executing on the hardware processor of the system; determining, via the adaptive trust profile system, whether an event of the plurality of events enacted by the entity is of analytic utility, the event being of analytic utility indicating an entity behavior associated with the event represents a security risk; generating, via the adaptive trust profile system, contextual information about the event based upon an entity profile, the contextual information comprising information relating to a particular entity behavior; deriving, via the adaptive trust profile system, a meaning from the contextualized information associated with the event, the meaning including an inference of an intent of the entity associated with the event; and, updating, via the adaptive trust profile system, the adaptive trust profile of the entity based upon the contextual information about the event and the intent of the entity associated with the event.
 28. The system of claim 27, wherein: the adaptive trust profile system comprises an event enrichment module, the event enrichment module performing an event enrichment operation.
 29. The system of claim 27, wherein: the adaptive trust profile system comprises a meaning derivation module, the meaning derivation module performing a meaning derivation operation, the meaning derivation operation deriving the meaning from the contextualized information.
 30. The system of claim 27, wherein: the adaptive trust profile system comprises a contextualization module, the contextualization module performing a contextualization operation, the contextualization operation generating the contextual information.
 31. The system of claim 27, wherein: the adaptive trust profile system comprises an anomaly detection module, the anomaly detection module performing an anomaly detection operation.
 32. The system of claim 21, wherein: the anomaly detection operation determines whether the event of the plurality of events is of analytic utility.
 33. A non-transitory, computer-readable storage medium embodying computer program code for generating and managing an adaptive trust profile, the computer program code comprising computer executable instructions configured for: monitoring a plurality of electronically-observable actions of an entity, the plurality of electronically-observable actions of the entity corresponding to a respective plurality of events enacted by the entity, the entity comprising a user entity; generating the adaptive trust profile based upon the plurality of actions of the entity, the adaptive trust profile being generated by an adaptive trust profile system, the adaptive trust profile comprising a collection of information describing an identity of the entity, the adaptive trust profile system executing on a hardware processor of an information handling system; determining, via the adaptive trust profile system, whether an event of the plurality of events enacted by the entity is of analytic utility, the event being of analytic utility indicating an entity behavior associated with the event represents a security risk; generating, via the adaptive trust profile system, contextual information about the event based upon an entity profile, the contextual information comprising information relating to a particular entity behavior; deriving, via the adaptive trust profile system, a meaning from the contextualized information associated with the event, the meaning including an inference of an intent of the entity associated with the event; and, updating, via the adaptive trust profile system, the adaptive trust profile of the entity based upon the contextual information about the event and the intent of the entity associated with the event.
 34. The non-transitory, computer-readable storage medium of claim 33, wherein: the adaptive trust profile system comprises an event enrichment module, the event enrichment module performing an event enrichment operation.
 35. The non-transitory, computer-readable storage medium of claim 33, wherein: the adaptive trust profile system comprises a meaning derivation module, the meaning derivation module performing a meaning derivation operation, the meaning derivation operation deriving the meaning from the contextualized information.
 36. The non-transitory, computer-readable storage medium of claim 33, wherein: the adaptive trust profile system comprises a contextualization module, the contextualization module performing a contextualization operation, the contextualization operation generating the contextual information.
 37. The non-transitory, computer-readable storage medium of claim 33, wherein: the adaptive trust profile system comprises an anomaly detection module, the anomaly detection module performing an anomaly detection operation.
 38. The non-transitory, computer-readable storage medium of claim 37, wherein: the anomaly detection operation determines whether the event of the plurality of events is of analytic utility.
 39. The non-transitory, computer-readable storage medium of claim 33, wherein: the computer executable instructions are deployable to a client system from a server system at a remote location.
 40. The non-transitory, computer-readable storage medium of claim 33, wherein: the computer executable instructions are provided by a service provider to a user on an on-demand basis. 